fix: remove unnecessary b2b_users storage on vbase

[enzomerca]

What problem is this solving?

The b2b_users data on vbase was only being written but never read. This PR removes this entity usage from vbase.

This data was originally read on the checkPermissions function, but it was removed months ago due to an issue with vbase.

Now, this is the use cases that writes the most to vbase, but is its data is never read, hence, there is no point in keeping it.

[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 = 9, PR deletions = 24

Generated by 🚫 dangerJS against b06b47f

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[wender]

LGTM

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 1.44.6 → 1.44.7

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 [email protected]

After that your app will be updated on all accounts.

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