feat(attributes): add sentry.dsc.project_id as an attribute

[constantinius]

Description

Required for Dynamic Sampling

Contributes to https://linear.app/getsentry/issue/TET-2341/write-root-transaction-and-project-onto-every-span-in-relay

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 pii (i.e. maybe or true. Use false 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

[linear-code]

TET-2341

[github-actions]

Semver Impact of This PR

🟡 Minor (new features)

📋 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.dsc.project_id as an attribute by constantinius in #358

• Add calculated performance scores by loewenheim in #355
• Add rpc.response.status_code attribute by alexander-alderman-webb in #352
• Add rpc.method attribute by alexander-alderman-webb in #351
• Add app vitals start attributes by buenaflor in #353
• Add process.runtime.engine.* attributes by chargome in #347

Bug Fixes 🐛

• (attributes) Change several deprecation statuses to normalize to align with ingestion paths by constantinius in #350
• (create) Replace angle brackets in file names by loewenheim in #356

Internal Changes 🔧

• (gh) Remove myself from CODEOWNERS by lcian in #354
• Bump vulnerable js packages by chargome in #359

---

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

[shellmayr]

Is this the best name for this attribute? @Dav1dde you might have some ideas about naming here, I think maybe we have a convention in relay already. What I know is that we use this as count_per_root_project in generic metrics, but maybe we can come up with a clearer name.

[Dav1dde]

I think project_id would fit, since we already have public_key which is also scoped to the DSC and therefor always the "root" -> the root is implied through the DSC.

But this is pretty confusing if one isn't familiar with DS(C)

[constantinius]

If the namespace dsc is enough to distinguish it then I'm fine with that. sentry.dsc.transaction also denotes the trace root transaction, so I guess this is fine here. Will change it to that.

[constantinius]

@Dav1dde done and also changed project ID type to integer, hope thats fine