Update Ironbank

This MR contains the following updates:

Package	Update	Change
gluon	patch	0.5.9 -> 0.5.12
ironbank/opensource/grafana/tempo (source)	minor	2.5.0 -> 2.6.1
ironbank/opensource/grafana/tempo-query (source)	minor	2.5.0 -> 2.6.1
registry1.dso.mil/ironbank/opensource/grafana/tempo (source)	minor	2.5.0 -> 2.6.1
registry1.dso.mil/ironbank/opensource/grafana/tempo-query (source)	minor	2.5.0 -> 2.6.1

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: 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.

Upgrade Notices

• BREAKING CHANGE tempo-query is no longer a Jaeger instance with grpcPlugin. It’s now a standalone server. Serving a gRPC API for Jaeger on 0.0.0.0:7777 by default. [PR 3840]

docs/DEVELOPMENT_MAINTENANCE.md

@@ -159,13 +159,13 @@ annotations:
   repository: registry1.dso.mil/ironbank/opensource/grafana/tempo-query
 ```
 
-- Ensure `tempoQuery.enabled` is true
+- Ensure `tempoQuery.enabled` is __false__
 
 Note: [this](https://github.com/grafana/helm-charts/commit/4c77fa7b3a54977d094071b446ff8b5b86982858) upstream commit disabled `tempo-query` by default in the chart. Evidently this is because `tempo-query` was always meant as a shim between Tempo and Grafana, but it hasn't been necessary [since 7.5.0](https://github.com/grafana/tempo/issues/456#issuecomment-815813684), as Grafana is capable of querying Tempo directly now.
 
-Currently, Big Bang uses `tempo-query` for Cypress testing and users may expect a basic web interface for Tempo without Grafana (Tempo has non natively, only a HTTP API). This may be changed in an upcoming release, but we will keep utilizing `tempo-query` for the benefits of the interface.
+Previously, Big Bang used `tempo-query` for Cypress testing and to provide users a basic web interface for Tempo without Grafana (Tempo offers only an HTTP API natively). This was changed after breaking changes to the `tempo-query` deployment model were [introduced in version 2.6.0](https://grafana.com/docs/tempo/next/release-notes/v2-6/#other-breaking-changes). Other `tempoQuery` configuration settings remain below, in the event users wish to deploy it with the associated Iron Bank container image.
 ```yaml
-  enabled: true
+  enabled: false
 ```
 
 - Ensure `tempoQuery.resources` requests and limits are set