Chore/disable b2b flag

[brunoabreu]

What problem is this solving?

The "enables B2B behavior" flag is dangerous as it makes our GraphQL and navigation requests not cacheable. It was necessary because the user's token is required when fetching data from private sales channels. However some months ago we managed to create a new solution based on the segment cookie.

We are deprecating this flag now. The first step is to disable it.

How to test it?

Beta version installed here: https://brunoh--b2bstore.myvtex.com/admin/app/cms/store

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 😞

[vtex-io-docs-bot]

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

• There's nothing new to document 🤔
• I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

• I just updated 🎉🎉

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 2.116.0 → 2.117.0

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy vtex.store@2.117.0

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖