ref(seer): Rewrite AutofixRepositories using the new /seer/repos/ endpoints

[ryan953]

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

[github-actions]

Story previews

Preview the stories changed in this PR on the Vercel deployment:

• app/components/seer/projectDetails/autofixRepositoriesList.stories.tsx

_{Preview deployment: https://sentry-7nx3jdfo7.sentry.dev}

[github-actions]

📊 Type Coverage Diff

Metric	Before	After	Delta
Coverage	93.70%	93.70%	±0%
Typed	132,876	132,936	🟢 +60
Untyped	8,937	8,937	±0

🔍 1 new type safety issue introduced

Non-null assertions (!) (1 new)

File	Line	Detail
static/app/components/seer/legacy/addAutofixRepoModal.tsx	162	filteredRepositories[virtualItem.index]!

This is informational only and does not block the PR.

[billyvg]

Suggested change

	// Save the whole form?
	// const {mutateAsync: handleFormSubmit} = useMutation(
	// getMutateSeerProjectReposOptionsReplaceRepos({
	// organization,
	// project,
	// queryClient,
	// })
	// );

[cursor]

Cursor Bugbot has reviewed your changes and found 4 potential issues.

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

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

[sentry]

Bug: The empty state message logic in the repository selection modal is inverted, showing the wrong message for "no search results" versus "all repos already added".
_{Severity: MEDIUM}

Suggested Fix

The conditional logic for the empty state message should be corrected. Instead of checking selectedExternalIds.length, the logic should differentiate between two scenarios: an empty list due to a user's search query yielding no results, versus an empty list because all available repositories have already been added to the project.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: static/app/components/seer/legacy/addAutofixRepoModal.tsx#L147-L150

Potential issue: The logic for displaying an empty state message in the
`addAutofixRepoModal` is flawed. The condition `selectedExternalIds.length ===
filteredRepositories.length` is used to decide between showing "No matching repositories
found" and "All available repositories have been added". When the list of
`filteredRepositories` is empty, this condition incorrectly depends on whether the user
has selected items within the modal, rather than the reason for the list being empty.
This results in showing "All available repositories have been added" when a search
yields no results, and "No matching repositories found" when all repositories are
already connected, which is confusing for the user.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[sentry]

Bug: The check preventing selection of more than MAX_REPOS_LIMIT (8) repositories was removed, allowing users to add more than the intended maximum number of repos.
_{Severity: MEDIUM}

Suggested Fix

Reintroduce the guard within the handleToggleRepository function. Before adding a new repository to the selectedExternalIds state, check if selectedExternalIds.length is already greater than or equal to MAX_REPOS_LIMIT. If it is, prevent the addition and return the existing state.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: static/app/components/seer/legacy/addAutofixRepoModal.tsx#L95-L98

Potential issue: The `handleToggleRepository` function was refactored to remove a check
that prevented users from selecting more than `MAX_REPOS_LIMIT` (defined as 8)
repositories. While a `useEffect` hook shows an alert when the limit is reached, it does
not prevent the user from continuing to select more repositories. The submit handler and
the backend endpoint also lack validation to enforce this limit. This allows a user to
add more than the maximum of 8 repositories to a project for Autofix, which could lead
to unexpected backend behavior or violate system constraints.

_{Did we get this right? 👍 / 👎 to inform future reviews.}