Describe the issue

Carry out the Part 1/2 restructuring proposed in the investigation, migrating/renaming scripts into the new directory layout from #12925, and updating every internal and external reference (cron, Ansible, SOPs, other repos) so behavior is unchanged. This ticket covers the subset of scripts tracked in #12934 (Part 1 list). All work should land with atomic PRs and clear dependency ordering.

Context

• Overall target tree: see restructuring initiative (#12925).
• This is the implementation companion to #12934 (investigation Part 1/2).

Scope (Part 1/2 set)

Replace with the exact list from the final sheet resolution of #12934.
For each item, we will:
- Move to the new path; rename as per the convention file if required.
- Update imports/calls between scripts.
- Update systemd timers/cron/Ansible roles.
- Update docs/SOPs.

Dependencies (PR chain)

• Create these PRs and paste links before starting merges.
• releng (this repo): Moves/renames + internal references (PR-A).
• Ansible/infra (PR-B) → must merge before any timers trigger new paths.
• Docs/SOPs (PR-C) → can merge alongside PR-A but publish after deploy.
• Any other repos referencing these scripts (PR-D…).

The scripts listed under Part 2/2 (#12935) are out of scope unless explicitly shared/dependent. As mentioned in our calls, we will move the paths now and URLs for Forgejo separately at the time of migration.

Acceptance criteria

• All review comments in #12934 acknowledged/addressed.
• New paths/names match the directory schema from #12925.
• All internal and external invocations/imports/callers updated.
• Docs/SOPs reflect the new paths.
• Monitor the scripts timely in error messages, IRCs, tickets, etc for any relevant issues.

• When do you need this? (YYYY/MM/DD)

Ideally, the work is being done for this since, start of this week (September 22/23), but I decided to have this merged by next Wednesday. If there are any blockers, please communicate.

• When is this no longer needed or useful? (YYYY/MM/DD)

When will we not release Fedora anymore!

• If we cannot complete your request, what is the impact?

Migration for forgejo will be affected.

Please check https://www.fedorastatus.org/ for any known
outages before filing issues on an outage.