fix(build): Do not reference const in object

[JPeer264]

Description

The only thing which changes is the way how the constants are used within an object:

export const ATTRIBUTE_TYPE: Record<string, AttributeType> = {
-  [AI_CITATIONS]: 'string[]',
+  'ai.citations': 'string[]',
};

When having following code ESBuild is not able to tree-shake ATTRIBUTE_TYPE:

import { ANY_CONSTANT } from '@sentry/conventions';

console.log(ANY_CONSTANT);

When removing the references in the objects ESBuild is now able to tree-shake ATTRIBUTE_TYPE, as the constants are not referenced anymore 🤷

seems like this is the reason: evanw/esbuild#4373

PR Checklist

• I have run yarn test and verified that the tests pass.
• I have run yarn generate to generate and format code and docs.

If an attribute was added:

• The attribute is in a namespace (e.g. nextjs.function_id, not function_id)
• I have used the correct value for apply_scrubbing (i.e. manual or auto. Use never only for values that should never be scrubbed such as IDs)

If an attribute was deprecated:

• I've followed the policies described in CONTRIBUTING.md

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

• (attributes) Add sentry.status and sentry.trace.status by mjq in #453

Bug Fixes 🐛

• (build) Do not reference const in object by JPeer264 in #457

---

_{🤖 This preview updates automatically when you update the PR.}

[Lms24]

Thanks for looking into and fixing this!

(I'm gonna cut a conventions release after we merge this so that we can properly use the package in the JS SDK)