fix: adjust b2b-organizations-graphql integration

[Rudge]

What problem is this solving?

• We have an integration between storefront-permissions and b2b-organizations, and it is necessary to validate authentication in the request. But for some reason the storefront-permissions can't forward the cookie headers, and the token doesn't come in b2b-organization-graphql.

So, we change the integration structure and the graphql server intermediation to use the header x-vtex-caller as vtex.storefront-permissions and allow in b2b-organizations.

How should this be manually tested?

• Login in the b2b 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 😞

[github-actions]

	Messages
📖	❤️ Thanks!
📖	🎉 PR additions = 15, PR deletions = 16

Generated by 🚫 dangerJS against 9157472

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

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

See analysis details on SonarCloud

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 1.39.2 → 1.39.3

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. 📖