#42939)

This PR implements prioritize by project bias.

In detail: 
We run celery task every 24 at 8:00AM (UTC randomly selected) for every
ORG (we call it *prioritise by project snuba query* ) and all projects
inside this org, and for a given combination of org and projects run an
adjustment model to recalculate sample rates if necessary.

Then we cache sample rate using redis cluster ->
`SENTRY_DYNAMIC_SAMPLING_RULES_REDIS_CLUSTER` using this pattern for
key: `f"ds::o:{org_id}:p:{project_id}:prioritise_projects"`.

When relay fetches `projectconfig` endpoint we run `generate_rules`
functions to generate all dynamic sampling biases, so and we check if we
have adjusted sample rate for this project in the cache, so we apply it
as **uniform bias**, otherwise we use default one.

Regarding *prioritize by project snuba query* is cross org snuba query
that utilizes a new generic counter metric, which was introduced in
[relay]( getsentry/relay#1734)
`c:transactions/count_per_root_project@none`.

TODO:
- [x] Provision infrastructure to run clickhouse clusters for the
counters tables. This is primarily dependent on ops
- [x] Start running the snuba consumers to read and write to the
counters table. SnS can work on this
- [x] Add unit-tests;
- [x] Update snuba query using new metric
- [x] Hide behind feature flag 


related PRs:
- Implement new metric in relay:
getsentry/relay#1734
- Add org generic counters [TET-695]
getsentry/snuba#3708
- Introduce new storages for counters in snuba
getsentry/snuba#3679
- Add feature flag: https://github.com/getsentry/getsentry/pull/9323
- Add cross organization methods for the string indexer #45076
#45076

[TET-695]:
https://getsentry.atlassian.net/browse/TET-695?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

---------

Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
Co-authored-by: Nar Saynorath <nar.saynorath@sentry.io>