When Identifying a product tag for a given offering SKU use the LEVEL_1 & LEVEL_2 attributes. 

Acceptance Criteria

• If LEVEL fields are specified on a product tag then they are used for identification, if not, then they are not used. 
• LEVEL fields are an alternative to and take precedence over the ProductName attributes. If a product tag is matched via a LEVEL_1 & LEVEL_2 then it will override the ProductName. 
• The LEVEL attributes can be used in combination with ENG IDs, Metered, and other attributes on a SKU. 
• The LEVEL_3 field is unused by SKUs at this time.
• This will be tested using the Ansible Product Config
• In the product tag config, the attribute keys are specified as "level1" & "level2"
• This can be tested using the product tag config created in  SWATCH-2572 
• Update swatch-support-script imports to include level1 and level2
  •  [lburnett] There doesn't seem to be any helper import scripts that need updating in either the main repo or the swatch-support scripts.  The import scripts in swatch-support scripts act on the whole table and not individual columns.