Add organization restore route to the routes snapshot

What does this MR do and why?

This adds the organization restore route to the routes snapshot. It pairs with gitlab-org/gitlab!261304 (merged), which adds POST /api/:version/organizations/:id/restore.

The route needs authentication, so no new rule is needed in src/routes.ts. The new route matches /api/* with no claim, the same as the other /api/:version/organizations/:id routes. Route guards did not change.

This MR should merge first, so the cells-routes:router-in-sync job on the GitLab MR can pass.

References

• Paired GitLab MR: gitlab-org/gitlab!261304 (merged) (@rymai asked for this router MR in its review)

How to set up and validate locally

1. Download the route from the GitLab branch (it lives in the community fork):

   GITLAB_ROUTES_PROJECT=gitlab-community/gitlab-org/gitlab npm run download-gitlab-routes -- 599346-organization-restore-api

   It printed 5093 → 5094 routes (1 added, 0 updated, 11 not changed on this branch, 27 kept that only the router has).

2. Run npm run generate-route-guards. src/generated_route_guards.ts did not change.

3. Run npm run test -- routes.spec.ts. Before the snapshot update, the only difference was the new route (with and without .json, and the dotted example), all matching /api/* with a null claim. After -u:

   Snapshots  1 updated
   Test Files  2 passed (2)
        Tests  19 passed (19)

The rest runs in the pipeline.

Implemented with AI assistance; I reviewed and tested the changes.

MR acceptance checklist

Evaluated against the MR acceptance checklist.