feat(mariadb): Force+Replace sync-option on Backup when pvc.enabled (#64

)

Backup.spec.storage is immutable (operator vbackup webhook), so migrating an existing
Backup from a static volume to a PVC fails an ArgoCD apply with 'field is immutable'.
When backup.pvc.enabled, annotate the Backup with argocd.argoproj.io/sync-options:
Force=true,Replace=true so ArgoCD delete+recreates it. Lets hotcrp instances migrate
to nfs-archive PVC backups via pure git. Bumps 0.1.26 -> 0.1.27.

feat(mariadb): optional dynamically-provisioned PVC for logical backu…

…ps (#62)

Adds backup.pvc.{enabled,storageClassName,accessModes,size,annotations}. When
enabled, the chart creates <fullname>-backup-storage and the Backup mounts it via
storage.volume.persistentVolumeClaim, so a dynamic provisioner (nfs-subdir) auto-
creates the backing dir — no manual mkdir on the NFS server per instance. Default
off; storage pass-through unchanged when disabled. Bumps 0.1.25 -> 0.1.26.

chore(hotcrp): bump 0.3.11, re-vendor mariadb 0.1.27 (Backup Force+Re…

…place) (#65)

Refreshes Chart.lock 0.1.26 -> 0.1.27 so hotcrp packages the mariadb that adds the
Force=true,Replace=true sync-option on the Backup when backup.pvc.enabled. Lets the
remaining hotcrp instances migrate to nfs-archive PVC backups via pure git (ArgoCD
delete+recreates the immutable Backup) instead of a manual kubectl delete each.

chore(hotcrp): bump 0.3.10, re-vendor mariadb 0.1.26 (backup PVC supp…

…ort) (#63)

Refreshes Chart.lock 0.1.17 -> 0.1.26 so hotcrp packages the mariadb chart that
exposes backup.pvc (dynamically-provisioned backup storage). Enables switching
hotcrp instances off the static archivep02 NFS mount that needs a manual root
mkdir per instance. No hotcrp template changes; opt-in via db.backup.pvc in values.

feat(mediawiki): re-lock onto mariadb 0.1.25 (0.9.6)

mariadb 0.1.25 is now published, so regenerate the lock to bundle it
(0.9.5 shipped with 0.1.24 due to chart-releaser publish ordering).
Bump version so chart-releaser picks up the change.

fix(mediawiki): regenerate Chart.lock to fix out-of-sync digest

The lock was hand-edited in 7b49823 (version + digest typed by hand),
so cr package rejected it as out of sync with Chart.yaml. Regenerated
via 'helm dependency update', resolving to the published mariadb 0.1.24
with the correct digest.

fix(mediawiki): regenerate Chart.lock to fix out-of-sync digest

The lock was hand-edited in 7b49823 (version + digest typed by hand),
so cr package rejected it as out of sync with Chart.yaml. Regenerated
via 'helm dependency update', resolving to the published mariadb 0.1.24
with the correct digest.

fix(mediawiki): regenerate Chart.lock to fix out-of-sync digest

The lock was hand-edited in 7b49823 (version + digest typed by hand),
so cr package rejected it as out of sync with Chart.yaml. Regenerated
via 'helm dependency update', resolving to the published mariadb 0.1.24
with the correct digest.

fix(mediawiki): regenerate Chart.lock to fix out-of-sync digest

The lock was hand-edited in 7b49823 (version + digest typed by hand),
so cr package rejected it as out of sync with Chart.yaml. Regenerated
via 'helm dependency update', resolving to the published mariadb 0.1.24
with the correct digest.

FIX security-dashboard crashes on migration job

The db migration can't run because the project doesn't seem to be using
flask-migrate this time. DB migrations appears to be run in entrypoint
using only raw sql files, so the 'flask db migrate' command doesn't
work. Removed the job to fix.