chore: add open telemetry to api

[icazevedo]

What's the purpose of this pull request?

Considering the context, what is the problem we'll solve? Where in VTEX's big picture our issue fits in? Write a tweet about the context and the problem itself.

How does it work?

Tell us the role of the new feature, or component, in its context.

How to test it?

Describe the steps with bullet points. Is there any external reference, link, or example?

References

Spread the knowledge: is any content you used to create this PR worth sharing?

Extra tip: add references to related issues or mention people important to this PR may be good for the documentation and reviewing process

Checklist

You may erase this after checking them all 😉

PR Title and Commit Messages

• PR title and commit messages follow the Conventional Commits specification
  • Available prefixes: feat, fix, chore, docs, style, refactor, perf, and test

PR Description

• Added a label according to the PR goal - Breaking change, Features, Bug fixes, Chore, Documentation, Style changes, Refactoring, Performance, and Test
• Added the component, hook, or path name in-between backticks (``) - if applicable, e.g., ComponentName component, useWindowDimensions hook

Dependencies

• Committed the yarn.lock and bun.lockb file when there were changes to the packages

Documentation

• PR description
• Added to/Updated the Storybook - if applicable
• For documentation changes, ping @carolinamenezes or @PedroAntunesCosta to review and update

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nextjs-store-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 23, 2023 8:44pm

[vtex-sites]

Lighthouse Reports

Here are the Lighthouse reports of this Pull Request

📝 Based on commit f475a6b

Lighthouse Report by page
📎   /
📎   /apple-magic-mouse/p
📎   /office