[BojanG99]

Description (e.g. "Related to ...", etc.)

taf-server update inserts new redirects into the database, but the
running server only computes its in-memory map of repos-with-redirects
once at startup, so newly inserted redirects were invisible until a
restart.

Add POST /_internal/redirects/refresh, which re-queries the database
and replaces the cached set. The cache now lives behind an
Arc<RwLock<_>> so a refresh in one Actix worker/scope is visible to
all of them, instead of each clone of App holding its own copy.

The endpoint has no guard; external access is expected to be blocked
at the nginx layer (see openlawlibrary/publish-server).

Code review checklist (for code reviewer to complete)

• Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
• Title summarizes what is changing
• Commit messages are meaningful (see this for details)
• Tests have been included and/or updated, as appropriate
• Docstrings have been included and/or updated, as appropriate
• Standalone docs have been updated accordingly

Automated tests, benchmarks and linters

You can run the tests, lints and benchmarks that are run on CI locally with:

just ci

[n-dusan]

suggestion: would moving code to an api/internal/redirects be more consistent?