[Usage-based] Adjust `d_b_workspace_instance.attributedTeamId` to be not team-specific

[jankeromnes]

Is your feature request related to a problem? Please describe

Adjust d_b_workspace_instance.attributedTeamId to be not Team-specific, so that it can also explicitly include attributed User IDs when relevant.

This way, the usage component can simply group by this "attribution ID" without needing to join with other tables.

Describe the behaviour you'd like

Describe alternatives you've considered

Additional context

Optionally, we can also back-fill attribution IDs in the production DB from when the column was first deployed (as an ad-hoc, one-time prod DB fix).

[jankeromnes]

Relevant sync summary from Slack (internal):

We discussed that:

• Jan would drive the effort to fix this soon-ish
• we decided to have one column name usageAttributionId
• with prefixes (where the separator should be something not part of the ID, so not -)
• the migration does not backfill data. We handle prod manually by either:
  • setting userIds from the point in time we started adding teamIds (safe), or
  • remove all values that do not start with team