fix: normalize repoFullName to lowercase in validateRepoFullName

[Tet-9]

Summary

GitHub repository identity is case-insensitive, but admin endpoints
used exact-case matching. A request with Entrius/das-github-mirror
would fail to find a stored row of entrius/das-github-mirror, causing
valid repos to get "Repo not found" errors on registration and breaking
downstream backfill flows in getTokenForRepo.

Root Cause

validateRepoFullName returned the input as-is without normalization.
Both registerRepo and backfillRepo call it, so the raw casing flowed
directly into DB update and findOneBy queries.

Fix

One line — .toLowerCase() on the return value of validateRepoFullName.
Since all admin paths go through this validator, normalization is enforced
at the single entry point rather than scattered across call sites.

Fixes entrius/gittensor#1214

[anderdc]

This lowercases the admin input but repo rows store GitHub's canonical casing — installation.handler.ts:44,52 insert repository.full_name unnormalized. For any repo whose canonical name has uppercase, lowercasing the input makes registerRepo's update({ repoFullName }) (admin.controller.ts:126) and getTokenForRepo's findOneBy({ repoFullName }) (github-fetcher.service.ts:198) miss the row — a regression on the previously-working exact-case path.

The repo already handles case-insensitive repo matching correctly in repos.service.ts:28 and pulls.service.ts:51 with LOWER(repo_full_name) = LOWER($1). Apply that same pattern to the registerRepo update and the getTokenForRepo lookup instead of normalizing input only — input-only normalization misses mixed-case repos since storage keeps canonical casing.

[igeabdulrahmanikeoluwa-str]

This lowercases the admin input but repo rows store GitHub's canonical casing — installation.handler.ts:44,52 insert repository.full_name unnormalized. For any repo whose canonical name has uppercase, lowercasing the input makes registerRepo's update({ repoFullName }) (admin.controller.ts:126) and getTokenForRepo's findOneBy({ repoFullName }) (github-fetcher.service.ts:198) miss the row — a regression on the previously-working exact-case path.

The repo already handles case-insensitive repo matching correctly in repos.service.ts:28 and pulls.service.ts:51 with LOWER(repo_full_name) = LOWER($1). Apply that same pattern to the registerRepo update and the getTokenForRepo lookup instead of normalizing input only — input-only normalization misses mixed-case repos since storage keeps canonical casing.

Good catch! You're right — input-only normalization misses repos stored with GitHub's canonical casing. Updated to use LOWER(repo_full_name) = LOWER(:repoFullName) in both registerRepo's update and getTokenForRepo's lookup, following the same pattern already used in repos.service.ts and pulls.service.ts

Already fixed now