As a developer, I'd like configuration for existing products to be consumable from swatch-product-configuration, so that swatch components can function without tag profile.

TagMetric values will be moved into their respective subscription's metrics object.

• UOM will be dropped

TagMappings values will be moved w/ the following logic:

• engIds will be moved to the fingerprint section of the corresponding subscription (except for RHEL)
• engIds specific to variants will be copied to the variant's engineering_id fields.
• roles will be moved to the variants section's field.
• productNames will be moved to the variants section's field.
• arches will be moved to the subscription's fingerprinting object.

TagMetadata changes:

• finestGranularity will be dropped and instead inferred from the presence of PrometheusMetric objects (finestGranularity = HOURLY for PrometheusMetric, DAILY otherwise)
• billingModel will be dropped. Instead we'll infer based on the value of systems' billingMarketplace value - if it's set, we assume it can be billed.
• defaultSla, defaultUsage moved to defaults object.

Note: We want to use a convention of $Platform/$Subscription_Name.yaml (e.g. RHEL/RHEL_for_x86.yaml).

See rough draft example at https://gist.github.com/kahowell/ecaa66021d55e3c14a9cc4f56a494ffe

See https://docs.google.com/document/d/1qrYBxqbf9FOBKWAOYD6RDyQoj8AzNomF4cHRkAEhc9o/edit# for rationale and design

Done:

• All configuration in tag_profile has equivalent definitions in swatch-product-configuration (except as noted above).

QE Notes:

Changes will be made in ConfigParser and smqe-tools