a small step towards HAC-394 and HAC-4762.

Overall desire to align with backend api properties and values.

The v1 wizard component BillingModelSection can set billing_model field to value 'standard-trial', which is not a real billing model.  We have several ugly kludges translating that to billing_model 'standard' and product 'OSDTrial'.
AFAICT it's all dead code and can be exorcised.
EDIT: v2 wizard BillingModel.tsx also uses billingModels.STANDARD_TRIAL

Implementation Details

• standardize and normalize the usage of 'billing model' and 'product' in the v2 OSD wizard.
  • Billing Models: standard, marketplace
  • Product: osd, osd-trial
  • Marketplace: Red Hat, Google Marketpace

QE: Areas to test for regressions

From user with quota for both OSD & OSDTrial:

1. Clusters > Create > OSD "Create Cluster" button
2. Inside wizard check that Subscription type defaulted to "Annual"
3. Switch Infrastructure type to "Red Hat cloud account"
4. Switch Subscription type to "Free trial"
5. Check "Red Hat cloud account" got disabled and CCS was automatically chosen.
6. complete wizard, check that Review screen shows "Free trial" and an OSDTrial cluster actually gets created.
7. Clusters > Create > OSDTrial "Create Trial Cluster" button
8. Inside wizard check that Subscription type defaulted to "Free Trial"
9. Check that Infrastructure type defaults to CCS and "Red Hat cloud account" option is disabled
10. Switch Subscription type to to "Annual"
11. Check that Infrastructure type "Red Hat cloud account" became available (but CCS remains chosen)
12. complete wizard, check that Review screen shows "Annual" and an OSD cluster actually gets created.