feat: add directive to validate auth token

[Rudge]

What problem is this solving?

Some operations that return sensitive information don't validate the admin or store token. So I added the directive @checkUserAccess to validate the token before calling the operation.

I improved the log warning for token validation by logging the operation that has an invalid token.

The operations were previously mapped in the task, and with the directive that was added @auditAcess.

How should this be manually tested?

• Call the operation without cookie and header

curl --location 'https://b2bsuite.myvtex.com/_v/private/graphql/v1' \
--header 'Content-Type: application/json' \
--data '{
    "query": "query users {\n listAllUsers {\n id\n orgId\n costId\n name\n email\n roleId\n userId\n }\n }",
    "variables": {}
}'

Workspace

[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 = 209, PR deletions = 162

Generated by 🚫 dangerJS against e98efe3

[mairatma]

Code lgtm, but just to be sure: did the metrics from the existing @auditAccess directive already show that we can turn on this token validation without breaking existing stores? Just worried that this might cause problems for callers that are using it wrong, specially since we're near BF.

[mairatma]

Also, there's a check failing right now. It's just about selecting a checkbox on the doc question post from the bot though.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
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.37.3 → 1.38.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 [email protected]

After that your app will be updated on all accounts.

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