bump rusty_alloc-api to =2.2.6

[Ttimmahlax]

Automated dependency rollout by remade-updater.

Moves rusty_alloc-api to =2.2.6 across every repository that declares it, so the portfolio does not end up straddling two versions of one crate.

This pull request is one of a set. None of them merge until all of them are green -- a half-merged rollout is the state this tooling exists to prevent.

Generated from the manifests themselves; nothing here is hand-maintained.

[Ttimmahlax]

Held out of wave 1 of the portfolio release campaign; not merged.

tests/peak_heap.rs fails on ubuntu-latest only, reproducibly (re-run gave the same result):

peak-heap ceilings exceeded: [(quiet, 8000, 5, 126392, 125952)]

+440 bytes over the ceiling. main passes the same job today (d726f78), and the counter wraps System, not rusty_alloc, so the bump should not move it directly; the dev-dependency change is the only difference. That needs a Linux run with RUSTY_FLAC_PEAK_DUMP=1 to see which allocation grew before deciding whether the ceiling or the code moves.

Nothing downstream waits on this: rusty_alloc-api is a dev-dependency here, so consumers of rusty_flac are unaffected.

🤖 Generated with Claude Code

[Ttimmahlax]

Follow-up: the peak-heap failure is a flaky test, not this change.

• The re-run failed on a different row: (quiet, 512, 0, 38488, 37888), while the row that failed first (quiet 8000 5) came in at 125,492, under its ceiling.
• On Linux (WSL, rustc 1.99.0), tests/peak_heap.rs gives byte-identical numbers on main and this branch, with and without --features libm and with and without --nocapture: quiet 8000 5 = 125,492, quiet 512 0 = 37,588 on both.

So roughly 600 to 900 extra bytes land on whichever row happens to be running. The counter is a process-wide #[global_allocator], so it most likely also counts allocations made concurrently by the test harness's own threads. main passing today is luck. Worth fixing separately, e.g. counting only on the test's own thread, or running the measurement with --test-threads=1 and capture off.

Re-running the job; this merges on a green run.

🤖 Generated with Claude Code