Update Ironbank

This MR contains the following updates:

Package	Update	Change
bb-common	minor	1.5.0 → 1.6.0
gluon	patch	1.1.6 → 1.1.8
registry1.dso.mil/ironbank/sonarsource/sonarqube/sonarqube-community-build (source)	minor	26.8.0.126808-community → 26.9.0.129388-community
registry1.dso.mil/ironbank/sonarsource/sonarqube/sonarqube-community-build (source)	minor	26.8.0.126808 → 26.9.0.129388

Validation

• Latest-head CI pipeline: configuration checks and all default/SSO clean-install and upgrade lanes passed. The SSO CI profile uses fresh embedded H2; it does not validate database migration or data retention.
• k3d-dev: a PostgreSQL-backed 26.8 → 26.9 upgrade completed 25/25 database migrations, returned SonarQube to UP, and retained project UUID b834538f-ad7f-4ea8-b88d-ef9c747f37cc and PVC UID 02577df1-7bc9-41de-a026-d9daf9dddd8b. All three SonarQube Prometheus targets were UP.
• Follow-up: #228 tracks PostgreSQL-backed CI upgrade coverage.

Complete MR checklist

Assignee

• Followed upgrade instructions outlined in docs/DEVELOPMENT_MAINTENANCE.md
• Update Docs with new/updated steps as needed
• Tested and Validated Changes made with supporting info like logs or screenshots from test pipelines

Add supporting info below

Reviewer only

• Tested and Validated changes

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This MR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this MR, check this box

---

This MR was automatically generated by Renovate Bot.

Linked issues

Closes: #225 (closed)

Upgrade Notices

For persistent SonarQube Community Build installations backed by PostgreSQL, back up the database before updating to 26.9, then visit /setup to complete the database migration after deployment. See SonarSource's pre-update steps and Helm update procedure.