feat: Add missing GCP and FaaS attributes

[ericapisani]

Add faas.duration_in_ms, faas.entry_point, faas.identity, and gcp.project.id to the model and regenerate JS and Python attribute files.

These attributes were missing from the conventions despite being used in GCP and FaaS instrumentation. Adding them ensures SDKs have consistent, typed constants to reference rather than relying on raw strings.

[linear-code]

PY-2324

[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 ✨

Docs

• Add links to deprecated and aliased attributes by Lms24 in #396
• Add filtering capability by nsdeschenes in #395

Other

• Add missing GCP and FaaS attributes by ericapisani in #403

Bug Fixes 🐛

• Change type of sentry.dsc.project_id to string by elramen in #400

Internal Changes 🔧

• (publish) Automatically add PR numbers to attribute changelogs by Lms24 in #402

---

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

[Lms24]

Reading the slack thread, we should also add the current attributes (sent by the SDK in transaction mode) as deprecated attributes into conventions and mark them as replaced by the new ones. Feel free to do this in a follow-up PR if you prefer!

This allows us to do backwards/forwards coalescing at ingest/query time so that existing dashboards/queries/alerts remain functional.

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 39754ca. Configure here.}

[ericapisani]

@Lms24

Reading the slack thread, we should also add the current attributes (sent by the SDK in transaction mode) as deprecated attributes into conventions and mark them as replaced by the new ones. Feel free to do this in a follow-up PR if you prefer!

Correct me if I'm wrong, but in this case I don't think there's any attributes to mark as deprecated because these values are being sent as part of the extra property on an event in an event_processor rather than being added to spans via the set_data that we usually use.

[Lms24]

@ericapisani you're right, sorry, I didn't know they weren't sent as data before. So, no need to add and deprecate the old ones.

[Lms24]

I double-checked and we currently send a cloud.project_id attribute in JS that's only applied to GCP. I agree with your reasoning though to scope this attribute to the gcp namespace. Makes much more sense, given the other FAAS providers don't have the same project semantics as GCP.

Once this PR is merged, I'll open a PR to add the attribute from JS and deprecate it in favour of this one.