chore(deps): stack PatchRaptor updates #107-#111

[joshyorko]

Summary

• stack the unique dependency changes represented by chore(deps): update dependency go to v1.26.5 #107 through fix(deps): update module gopkg.in/yaml.v2 to v3 #111
• update the official Go toolchain from 1.26.3 to 1.26.5 across go.mod, GitHub Actions, and the Dagger runner
• keep the contained RCC developer toolkit on Go 1.26.3, the newest version currently available from Conda Forge
• update golang.org/x/term to v0.45.0 with its required golang.org/x/sys v0.47.0 dependency
• update gopkg.in/yaml.v2 to v2.4.0
• update the changelog and PatchRaptor policy so completed, unavailable, or invalid lanes do not keep reopening

Why the toolkit Go pin differs

The official Go 1.26.5 release is usable by actions/setup-go, go.mod, and the
Dagger golang image. The RCC developer toolkit has a different supply chain:
developer/setup.yaml asks RCC/micromamba to install the go package from
Conda Forge. Conda Forge does not currently publish go=1.26.5, so that pin
fails during holotree environment creation before unit tests or a local build
can start.

The toolkit therefore remains pinned to the newest available Conda Forge build,
Go 1.26.3. Renovate no longer applies its official golang-version datasource
to developer/setup.yaml; that contained pin should move only after the matching
Conda Forge package exists. This is an intentional source-availability boundary,
not uncoordinated version drift.

Stack resolution

• fix(deps): update module golang.org/x/term to v0.45.0 #109 includes the fix(deps): update module golang.org/x/sys to v0.47.0 #108 x/sys update, so both are represented by the same module changes.
• fix(deps): update module gopkg.in/yaml.v2 to v2.4.0 #110 and fix(deps): update module gopkg.in/yaml.v2 to v3 #111 currently produce identical trees: both resolve gopkg.in/yaml.v2 to v2.4.0. A v3 release cannot be used through the gopkg.in/yaml.v2 import path, so this PR disables that invalid major-update lane while retaining the separate existing gopkg.in/yaml.v3 module.
• chore(deps): update dependency go to v1.26.5 #107's Go 1.26.5 update is applied to official-Go surfaces. developer/setup.yaml is deliberately excluded from that Renovate manager because it installs Go from Conda Forge, where 1.26.5 is not available yet.
• Future official Go updates remain grouped across go.mod, Actions, and Dagger without breaking RCC holotree environment creation.

After this lands, the target versions and Renovate policy are present on main, so PatchRaptor should not recreate the superseded #107-#111 lanes.

Verification

• git diff --check 585b997...HEAD
• rcc run -r developer/toolkit.yaml --dev -t unitTests
• rcc run -r developer/toolkit.yaml --dev -t local
• built ./build/rcc version reports v18.17.6
• .github/renovate.json5 parses as valid JSON5
• GitHub Actions remains the authoritative Robot matrix; no additional local Robot run was used as a publication gate.