chore(repositories): Remove project and repo columns from SeerProjectRepository and RepositoryProjectPathConfig

[wedamija]

This cleans up writes and any remaining queries to project and repo in SeerProjectRepositoryandRepositoryProjectPathConfig`, and also removes all references to the columns to prepare for deletion.

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/migrations/1098_remove_old_fks.py src/sentry/seer/migrations/0016_remove_old_fks.py

for 1098_remove_old_fks in sentry

--
-- Alter unique_together for repositoryprojectpathconfig (0 constraint(s))
--
ALTER TABLE "sentry_repositoryprojectpathconfig" DROP CONSTRAINT "sentry_repositoryproject_project_id_stack_root_so_c371dfa7_uniq";
--
-- Alter field project on repositoryprojectpathconfig
--
ALTER TABLE "sentry_repositoryprojectpathconfig" ALTER COLUMN "project_id" DROP NOT NULL;
--
-- Alter field repository on repositoryprojectpathconfig
--
SET CONSTRAINTS "sentry_repositorypro_repository_id_e5400943_fk_sentry_re" IMMEDIATE; ALTER TABLE "sentry_repositoryprojectpathconfig" DROP CONSTRAINT "sentry_repositorypro_repository_id_e5400943_fk_sentry_re";
ALTER TABLE "sentry_repositoryprojectpathconfig" ALTER COLUMN "repository_id" DROP NOT NULL;
--
-- Moved repositoryprojectpathconfig.project field to pending deletion state
--
-- (no-op)
--
-- Moved repositoryprojectpathconfig.repository field to pending deletion state
--
-- (no-op)

for 0016_remove_old_fks in seer

--
-- Alter unique_together for seerprojectrepository (0 constraint(s))
--
ALTER TABLE "seer_projectrepository" DROP CONSTRAINT "seer_projectrepository_project_id_repository_id_f08c56d6_uniq";
--
-- Alter field project on seerprojectrepository
--
SET CONSTRAINTS "seer_projectrepository_project_id_9b6ca557_fk_sentry_project_id" IMMEDIATE; ALTER TABLE "seer_projectrepository" DROP CONSTRAINT "seer_projectrepository_project_id_9b6ca557_fk_sentry_project_id";
ALTER TABLE "seer_projectrepository" ALTER COLUMN "project_id" DROP NOT NULL;
--
-- Alter field repository on seerprojectrepository
--
SET CONSTRAINTS "seer_projectreposito_repository_id_1c1c52ec_fk_sentry_re" IMMEDIATE; ALTER TABLE "seer_projectrepository" DROP CONSTRAINT "seer_projectreposito_repository_id_1c1c52ec_fk_sentry_re";
ALTER TABLE "seer_projectrepository" ALTER COLUMN "repository_id" DROP NOT NULL;
--
-- Moved seerprojectrepository.project field to pending deletion state
--
-- (no-op)
--
-- Moved seerprojectrepository.repository field to pending deletion state
--
-- (no-op)

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 25898b6. Configure here.}

[cursor]

Project deletion fails with branch override FK violation

High Severity

When deleting a project, SeerProjectRepository is deleted via BulkModelDeletionTask, which performs a raw SQL DELETE bypassing Django's ORM cascade. However, SeerProjectRepositoryBranchOverride rows referencing those SeerProjectRepository rows are never explicitly deleted first. Since Django creates FK constraints as NO ACTION (not ON DELETE CASCADE) at the database level, the raw DELETE will raise an IntegrityError if any SeerProjectRepositoryBranchOverride rows exist. Previously, SeerProjectRepository had a direct project FK, so Django's ORM cascade from Project.delete() handled the entire chain automatically. Now that the FK is removed, explicit deletion of SeerProjectRepositoryBranchOverride before SeerProjectRepository is needed.

 

^{Reviewed by Cursor Bugbot for commit 25898b6. Configure here.}