fix: make gitly compile with current V (32 veb handlers missing ctx, FileInfo collision)

[metif12]

Summary

Master does not compile. This restores the build with no behaviour change.

Two independent defects, plus a name collision that only the first one hid:

  repo/file.v
- struct FileInfo {          # collides with os.FileInfo
+ struct RepoFileInfo {

  repo/repo_routes.v (and 8 other files)
- pub fn (mut app App) user_repos(username string) veb.Result {
+ pub fn (mut app App) user_repos(mut ctx Context, username string) veb.Result {

veb.v dispatches app.$method(mut user_context, ...args). Since method.args excludes the
receiver, a handler with one parameter has args.len == 1, so it falls into the no-argument
branch and the context is passed to a method that does not accept it. change_lang was the
only one-parameter handler, so it failed first and masked 31 others. The multi-parameter
handlers compiled, but silently received form values where they expected path parameters.

user_repos and handle_admin_edit_user already referenced ctx in their bodies without
declaring it, and call sites such as app.admin_users(mut ctx, '0') already passed it, so
this restores the signature the code was written against — see the merged #125.

The FileInfo collision surfaced once the frontend stopped erroring. Substituting it into
api.ApiSuccessResponse[T] made V resolve the bare name in the wrong scope, emitting
os__FileInfo as the declaration and main__FileInfo as the initialiser.

Evidence

Before — V checker, on v -d sqlite -d use_openssl -o gitly.exe . at 9594917:

C:/Users/xman/v/vlib/veb/veb.v:539:12: error: expected 2 arguments to method App.change_lang, but got 1

Then, after that one handler was fixed:

src.c:67159:64: error: invalid initializer
  os__FileInfo __return_array_value_16 = *(main__FileInfo*)(array_get(result, __return_array_idx_15));

After — v -d sqlite -o gitly.exe . exits 0 and produces gitly.exe:

EXIT=0
True

Test run, v -d sqlite test utils_test.v:

OK     182.329 ms D:/MyProjects/gitly/utils_test.v
Summary for all V _test.v files: 1 passed, 1 total. Elapsed time: 886790 ms, on 1 job. Comptime: 886574 ms. Runtime: 182 ms.

Only one test file was run deliberately. v test recompiles the whole project per file, and one
file costs ~887s of comptime with VJOBS=2, so the 44-file tracked suite is not runnable locally
(~11h estimated). Full validation is left to CI, which is why the red Windows and -autofree jobs
are tracked separately.

Also checked, and red before this change for unrelated reasons — v fmt -verify . reports 54
unformatted files, 44 of which this PR never touches. Not adding v fmt -verify as a blocking CI
step in the same change that reddens the gate.

Merge Danger

Door: Two-way. git revert restores the previous broken-but-known state, and no data, schema,
or on-disk format changes.

Blast Radius: Every route handler in the app. All 32 signatures change, but only to add the
context parameter the bodies already used. The risk is not the signatures, it is that they were
wrong for every request: handlers that took path parameters without ctx were receiving form or
query values, so pages like /:username/repos and /:username/:repo_name/branches could not have
resolved their own identifiers. This PR makes them compile; whether they now resolve correctly at
runtime is untested here and should be confirmed by a reviewer clicking through the affected routes.

RepoFileInfo is an internal type used only by handle_api_repo_files; the JSON shape is
unchanged, so the API response for /api/v1/repos/:id/tree/files is byte-identical.