feat(attributes): Add faas.invoked_* attributes

[andreiborza]

Adds the faas.* attributes emitted by the vendored JS AWS SDK instrumentation.

• invoked_name
• invoked_provider
• invoked_region

OTel sem conv for faas.* can be found at: https://opentelemetry.io/docs/specs/semconv/registry/attributes/faas/

[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 faas.invoked_* attributes by andreiborza in #481

• Add AWS DynamoDB instrumentation attributes by andreiborza in #479
• Add sentry.metric.source by klochek in #476
• Add faas.id (deprecated) in favor of cloud.resource_id by andreiborza in #475
• Add faas.execution (deprecated) in favor of faas.invocation_id by andreiborza in #473
• Add messaging attributes by s1gr1d in #469
• Add url.same_origin (deprecated) and http.request.same_origin (replacement) attributes by Lms24 in #456
• Add db.response.status_code by s1gr1d in #462

Other

• (ai) Add granular cost attributes for cache and reasoning by vgrozdanic in #461
• (js) Add _BASE attribute key exports for dynamic attribute keys by Lms24 in #471

Internal Changes 🔧

• (ci) Stop inheriting secrets for changelog-preview by tobias-wilfert in #463

---

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

[Lms24]

given that these attributes (according to otel) should be equal to more general attributes: Can we set the alias field and link to them?

No need to deprecate then, since they're also not deprecated in OTel. Though I wonder why OTel permits this duality 😅

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

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

^{Reviewed by Cursor Bugbot for commit 9c79791. Configure here.}

[Lms24]

As discussed offline: No need for the alias. These should be the same value but it's not a bidirectional relationship.

[andreiborza]

given that these attributes (according to otel) should be equal to more general attributes: Can we set the alias field and link to them?

No need to deprecate then, since they're also not deprecated in OTel. Though I wonder why OTel permits this duality 😅

I read that more as a "these should have equal value when set" but not necessarily that these are aliases of each other. As discussed, probably better to keep as is.