When commerce_pricelist module is enabled always control variation prices with pricelist

Problem/Motivation

By default product variation comes with the list_price and price base fields. These are used by default as price customer will pay for the product.

Eventually when pricelist module is enabled it serves the same purpose - the price/list_price defined as comerce_pricelist_item takes precedence over fallback value stored on the product variation entity. This is achieved with PricelistPriceResolver.

Now we may have 2 places where base prices, subject to further alterations via order processors, are defined. This can cause some confusion among administrators where to go in order to edit the price.

Proposed resolution

TBD

Remaining tasks

TBD

User interface changes

TBD

API changes

TBD

Data model changes

TBD