Improve users segmentation in Sentry

[rlinoz]

Tag big accounts:

• Count of workspaces
• Count of reports
• Count of personal details

Tag admins VS regular users

[sosek108]

This is more tricky.

Tags cannot be used for comparisons such as greater than > or lower than <. These are strings.

For comparison we could use other parameters, eg. attributes. But attributes are added on Span level (so new middleware should be added). Attributes are not indexed and therefore there were not intended for comparison so I'm not yet sure if using attribute is good call.

So from now we have these two ways:

1. use tag with bucketing system, eg. reports: 10-100
2. use attribute with raw value, eg. 23
3. combine both
4. use other props such as measurement

[sosek108]

• Cohort 1: 1 workspace, <60 reports 
• Cohort 2: 1 workspace, <300 reports,
• Cohort 3: ≤5 workspaces, <300 reports,
• Cohort 4: ≤10 workspaces, 4,676 workspaces
• Cohort 5: >10 workspaces, 3,442 workspaces
• Cohort 6: Owns at least one Collect workspace (potentially subject to upgrade) → 3,978 workspaces
• Cohort 7: → 9,386 workspaces
• Cohort 8: A! customers → 5,770 workspaces
• Cohort 9: Invoiced customers → 2,192 workspaces
• Cohort 10: Owns at least one workspace not at feature parity yet → 8,757 workspaces

[sosek108]

Here is the Draft PR: #81052

[sosek108]

Undrafted the PR #81052

I've added tags that groups our accounts based on the size. Next step would be to tag span with info if user is an admin, but... Are we able to get this info?