chore: migrate Overseerr manifests to Seerr

[luckycold]

Summary

• Renamed the app manifests folder from apps/overseerr to apps/seerr and rewired Flux kustomization paths.
• Updated Flux/Kustomization and Helm chart naming from Overseerr to Seerr where safe for migration.
• Kept namespace/release identifiers (overseerr) to preserve existing storage continuity during first Seerr startup migration.

Validation

• Ran kustomize build clusters/main/kubernetes successfully.
• Build output includes Kustomization named seerr with path clusters/main/kubernetes/apps/seerr/app and no build errors.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8f59a6f588

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep HelmRelease name stable during migration

Renaming this resource from overseerr to seerr turns the rollout into a delete+create for Flux, not an in-place update: the existing HelmRelease/overseerr will be pruned, and its deletion path uninstalls the tracked Helm release before the new object can reconcile it. In a live cluster this causes avoidable teardown/reinstall churn (and can remove chart-managed objects), which conflicts with the stated goal of preserving continuity during the Overseerr→Seerr transition.

Useful? React with 👍 / 👎.