ProductList V2 introduced a breaking change for accessing Magento Open Source

### Expected Behavior
Being able to query categories from Magento Open Source
### Actual Behavior
Category query adds a staged attribute that is only available to Adobe Commerce. It could be great to have the ability to control this behavior via an Osgi config.
The documentation does state that V2 version are only for Adobe commerce, the problem is if we use V1 versions for productlist and product the UI will be broken.
### Reproduce Scenario (including but not limited to)
Try the Venia Store sample with a Magento Open Source instance
#### Steps to Reproduce

#### Platform and Version
AEM 6.5.12
#### Sample Code that illustrates the problem
`@PostConstruct
protected void initModel() {
super.initModel();
if (categoryRetriever != null) {
categoryRetriever.extendCategoryQueryWith(c -> c.staged());
categoryRetriever.extendProductQueryWith(p -> p.staged());
}
}`
#### Logs taken while reproducing problem
{categoryList(filters:{category_uid:{eq:"MTQ="}}){uid,description,name,image,product_count,meta_description,meta_keywords,meta_title,url_key,url_path,staged}}

Start with the Venia Store sample and the ProductList V2 category query described in the issue, then trace the initModel snippet that adds staged fields through the AEM Commerce components. Reproduce against Magento Open Source on AEM 6.5.12; done means category queries work without Adobe Commerce-only attributes while the UI remains functional when product and product-list versions are selected.

Written by the indexing model from the issue text.