fix(auth): Adding scoping_organization_id to replica

[sentaur-athena]

Adding scoping_organization_id to both ApiTokenReplica and SystemToken. The reason is that we want to limit auth tokens that are scoped to a specific organizations to any other organization.
Context on why we need this is here: #81193

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
23171	1	23170	214

View the top 1 failed tests by shortest run time

tests.sentry.backup.test_comparators::test_default_comparators

Stack Traces | 0.394s run time

#x1B[1m#x1B[.../sentry/backup/test_comparators.py#x1B[0m:2162: in test_default_comparators
    insta_snapshot(serialized)
#x1B[1m#x1B[31mE   Failed: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#x1B[0m
#x1B[1m#x1B[31mE   Snapshot .../snapshots/test_comparators/test_default_comparators.pysnap changed!#x1B[0m
#x1B[1m#x1B[31mE   #x1B[0m
#x1B[1m#x1B[31mE   #x1B[0m
#x1B[1m#x1B[31mE   Re-run pytest with SENTRY_SNAPSHOTS_WRITEBACK=new and then use 'make review-python-snapshots' to review.#x1B[0m
#x1B[1m#x1B[31mE   #x1B[0m
#x1B[1m#x1B[31mE   Or: Use SENTRY_SNAPSHOTS_WRITEBACK=1 to update snapshots directly.#x1B[0m
#x1B[1m#x1B[31mE   #x1B[0m
#x1B[1m#x1B[31mE   #x1B[0m
#x1B[1m#x1B[31mE   --- #x1B[0m
#x1B[1m#x1B[31mE   #x1B[0m
#x1B[1m#x1B[31mE   +++ #x1B[0m
#x1B[1m#x1B[31mE   #x1B[0m
#x1B[1m#x1B[31mE   @@ -28,6 +28,7 @@#x1B[0m
#x1B[1m#x1B[31mE   #x1B[0m
#x1B[1m#x1B[31mE        - apitoken_id#x1B[0m
#x1B[1m#x1B[31mE        - application_id#x1B[0m
#x1B[1m#x1B[31mE        - organization#x1B[0m
#x1B[1m#x1B[31mE   +    - scoping_organization_id#x1B[0m
#x1B[1m#x1B[31mE        - user_id#x1B[0m
#x1B[1m#x1B[31mE      model_name: hybridcloud.apitokenreplica#x1B[0m
#x1B[1m#x1B[31mE    - comparators:#x1B[0m
#x1B[1m#x1B[31mE   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~#x1B[0m

To view more test analytics, go to the Test Analytics Dashboard
Got feedback? Let us know on Github

[github-actions]

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/hybridcloud/migrations/0017_add_scoping_organization_apitokenreplica.py ()

--
-- Add field scoping_organization_id to apitokenreplica
--
ALTER TABLE "hybridcloud_apitokenreplica" ADD COLUMN "scoping_organization_id" bigint NULL;
CREATE INDEX CONCURRENTLY "hybridcloud_apitokenreplica_scoping_organization_id_a73a089b" ON "hybridcloud_apitokenreplica" ("scoping_organization_id");

[wedamija]

Migration lgtm.

I'd recommend for https://github.com/getsentry/getsentry/pull/15812 to merge before you merge this. We've been having issues with migrations timing out during deploys