Load-balancer deployment retrofitted and upgraded on both clusters

Both clusters' load-balancer deployments were still on an older layout that pinned raw manifests, so nothing could track upstream releases automatically.

Changes. Replaced the raw-manifest overlay with the standard two-source deployment (upstream chart plus this repository's own configuration), and moved both clusters onto the current release. Update automation is now handled by the dependency bot alone, taking patch-level releases automatically.

One thing worth recording: the template ships without the configuration block that tells the dependency bot which files to read. Without it the bot runs, reports success and changes nothing — a silent no-op rather than an error. That block was added explicitly to both repositories.

Moving service addresses onto the new load-balancer pools is deliberately held back until the storage rebuild backlog has drained.