New appSettings: disableAggregateOffer and useImagesArray

[mamastrorilli]

What problem is this solving?

This PR contains 2 new appSettings (false by default):

• disableAggregateOffer
• useImagesArray

The first one is used to change the aggregateOffer in Offer, with these benefits:

• Greater clarity for Google: By using the Offer field for simple products, Google can better understand product features, show them to the most relevant users and position them more relevantly in search results.
• Improved user experience: Clearer and more precise markup can lead to richer and more informative search results, making it easier for the user to choose.
• Increased CTR (Click-Through Rate): Better indexing and richer search results can lead to increased visibility of your site, a clearer and more relevant message is more likely to be clicked by users.
• Increased conversions: A higher CTR, combined with a good user experience on the website, can lead to increased sales.

The second one is used to consider an array of images for the product, instead using only the first one

How should this be manually tested?

These ws can be used:
https://www.whirlpool.it/microonde-da-incasso-whirlpool-colore-acciaio-inox-amw-730ix-858773001900/p?workspace=pdt1142
https://www.whirlpool.it/microonde-da-incasso-whirlpool-colore-acciaio-inox-amw-730ix-858773001900/p?workspace=pdt1142disabled (appSettings set to false)

Screenshots or example usage:

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞