[HOLD for payment 2024-11-20] Implement attribute limitation for performance traces

[rinej]

Firebase Performance Monitoring has a limitation on the number of custom metadata attributes we can use for traces; it only allows up to five attributes. To work within this constraint, we need to implement a method to selectively limit which attributes are saved in Firebase, ensuring we stay within the allowed threshold.

Additionally, we need a solution that enables us to save all attributes for use in other tools, e.g. Grafana, where no such limitation exists.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.60-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [NoQA] Add generic way for attributes, limit custom attributes for firebase #51960

If no regressions arise, payment will be issued on 2024-11-20. 🎊

For reference, here are some details about the assignees on this issue:

• @rinej does not require payment (Contractor)

[melvin-bot]

Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

[mountiny]

Not a bug, performance monitoring improvement, no payment, closing