issue in ROSA v1 and v2.

Hypershift initializes billing_model form field to "standard" (v1; unset in v2?).
We have code to correct it to "marketplace-aws" on submission but that's too late — some quota computation during wizard uses incorrect params.
(For quota purposes, "marketplace-aws" maps to "marketplace" quota param.)

Quotas for Classic "standard" are all unlimited (cost: 0 => Infinity).
Quotas for HCP "marketplace" are finite, though I see high numbers for my user, so not sure if this has realistic effects.

ROSA v1 results from added logging in availableQuota function:

• Control plane — too early, billing_model not set yet but one query with {"product":"ROSA","billingModel":"marketplace","resourceType":"cluster"}
• Accounts and roles — billing_model not set yet
• Cluster settings > Details — wrong value set "billing_model": "standard" ; some queries like {"product":"ROSA","billingModel":"standard","cloudProviderID":"aws","isBYOC":true,"isMultiAz":false,"resourceType":"cluster"}

  -> Infinity

• Cluster settings > Machine pool — by this stage we already got "billing_model": "marketplace-aws", in redux-form. Many queries like {"product":"ROSA","cloudProviderID":"aws","isBYOC":true,"isMultiAz":false,"resourceName":"standard-16-7gd","billingModel":"marketplace-aws","resourceType":"cluster"}

  -> 3016

• Networking > Configuration — No queries use billing_model on this page, only some generic {"product":"ROSA","resourceType":"cluster"} -> Infinity
  but I suspect that should be adjusted
• Networking > CIDR ranges — same, no queries use billing_model but probably they should
• Cluster roles and policies — same
• Cluster updates — same
• Review — same .

• • "Debug: cluster request to be sent" shows what will be sent to backend has  "billing_model": "marketplace-aws",