chore: major update

[enzomerca]

What problem is this solving?

Generating new major version. This new version includes ACL feature. Now the following permissions are needed to view/edit organizations within the admin UI app:
Buyer Organizations / buyer_organization_view
Buyer Organizations / buyer_organization_edit

If you are updating to this major version, make sure to update the following apps (if you have then installed) to the following major versions:
- vtex.b2b-admin-customers@2.x
- vtex.b2b-checkout-settings@3.x
- vtex.b2b-my-account@2.x
- vtex.b2b-orders-history@2.x
- vtex.b2b-organizations@3.x
- vtex.b2b-organizations-graphql@2.x
- vtex.b2b-quotes@3.x
- vtex.b2b-quotes-graphql@4.x
- vtex.b2b-suite@2.x
- vtex.b2b-theme@5.x
- vtex.storefront-permissions-components@2.x
- vtex.storefront-permissions-ui@1.x

[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 🎉🎉

[github-actions]

	Messages
📖	❤️ Thanks!
📖	🎉 PR additions = 18, PR deletions = 3

Generated by 🚫 dangerJS against 0100e05

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 2.0.1 → 3.0.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.b2b-organizations@3.0.0

After that your app will be updated on all accounts.

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