not needed to call the whole category tree in some resolvers anymore

[jgfidelis]

What problem is this solving?

These changes are already made in search-graphql. its copied from there. The catalog fixed a bug and we now have these fields in the category by id api

https://fidelis--biscoind.myvtex.com/_v/private/[email protected]/graphiql/v1?query=query%20%7B%0A%20%20category(id%3A137)%20%7B%0A%20%20%20%20id%0A%20%20%20%20name%0A%20%20%20%20slug%0A%20%20%20%20href%0A%20%20%20%20children%20%7B%0A%20%20%20%20%20%20name%0A%20%20%20%20%20%20slug%0A%20%20%20%20%20%20id%0A%20%20%20%20%20%20href%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D

How should this be manually tested?

Workspace

Checklist/Reminders

• [ ] Updated README.md.
• [ ] Updated CHANGELOG.md.
• [ ] Linked this PR to a Clubhouse story (if applicable).
• [ ] Updated/created tests (important for bug fixes).
• [ ] Deleted the workspace after merging this PR (if applicable).

Screenshots or example usage

Type of changes

✔️	Type of Change
_	Bug fix
_	New feature
_	Breaking change
_	Technical improvements

Notes

[vtex-io-ci-cd[bot]]

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:

• [x] Patch

• [ ] Minor

• [ ] Major

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[bot]]

Beep boop :robot:

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

• [x] There's nothing new to document :thinking:
• [ ] I'll do it later :disappointed:

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

• [ ] I just updated :tada::tada: