GQL: Variant can be both a float or an object(price range)

[mikemurray]

Issue Description

The price field for Variants can be either a float or an. object e.g. { range, min, max }. This is bad as the type is changing for a field that is labeled as a Float in the GQL schema.

Possible Solution

The data must have a consistent form, regardless of if it's a variant, option or variant with options.

In the simple-pricing plugin

• The Product and Variant schema extensions should have the field pricing: ProductPricingInfo field, and properly resolve that field as best a possible.
• We are then, discouraging the use of price and compareAtPrice and instead urge users to use pricing instead.
• The mutations for updateVariantPrice should still work