fix(graphql): expose repository field on UpdateRepositoryPayload

[sentry]

Fixes an issue where querying repository on UpdateRepositoryPayload resulted in a GraphQLError: Cannot query field 'repository' on type 'UpdateRepositoryPayload'.

Changes

• Added repository: Repository field to UpdateRepositoryPayload in update_repository.graphql
• Updated resolve_update_repository to return {"repository": repo}
• Returned repo from UpdateRepositoryInteractor.execute

Legal Boilerplate

Look, I get it. The entity doing business as "Codecov" is owned by Harness, Inc. In 2026 Harness acquired Codecov and as a result Harness is going to need some rights from me in order to utilize my contributions in this 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 Harness can use, modify, copy, and redistribute my contributions, under Harness's choice of terms.

Fixes API-F8W

_{@sentry <feedback>: Autofix iterates on these changes
@sentry stop iterating: Autofix stops iterating on this run}

_{This PR was automatically generated by Sentry. You can adjust this setting at any time.}

---

Note

Low Risk
Adds a response field and return value for an existing update flow; no changes to auth, validation, or persistence logic beyond surfacing the saved repository.

Overview
Fixes updateRepository so clients can select repository on UpdateRepositoryPayload instead of hitting a schema error.

The GraphQL payload type now declares repository: Repository, the resolver returns {"repository": repo} after the command runs, and UpdateRepositoryInteractor.execute return repo so the updated record is available to the mutation response.

^{Reviewed by Cursor Bugbot for commit e7dc00c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[sentry]

⚠️ Sentry needs additional GitHub App permissions

The Sentry GitHub App installation for this repository is missing permissions it needs to keep iterating on this pull request to get CI passing.

Review and accept the updated permissions to let Seer continue: https://github.com/organizations/codecov/settings/installations/86101127/permissions/update