fix: support maximum queued concurrency

[jonathanong]

Summary

• accept GitHub Actions concurrency.queue: max at workflow and job scope
• reject dynamic, non-string, and unsupported queue policies
• preserve reusable-workflow typecheck coverage when queued concurrency is enabled

Root cause

The concurrency schema recognized only group and cancel-in-progress. A valid workflow using GitHub's FIFO queue: max policy was therefore omitted from the reusable-workflow catalog, which made every downstream typecheck behind that call graph unreachable to tsconfig-gate-coverage.

Validation

• cargo test -p no-mistakes tsconfig_gate_coverage --lib (473 passed)
• cargo clippy -p no-mistakes --lib --tests -- -D warnings
• cargo fmt --all -- --check
• cargo run -q -p no-mistakes -- check
• git diff --check

Related issues

• Closes jonathanong/filaments#9333
• Refs jonathanong/filaments#9225; the downstream migration remains open until it consumes the released fix.

Follow-ups

None.

Shepherd Journal

• Codecov report was transient: JavaScript patch coverage was complete while the Rust coverage job was still active, so no code change was warranted.

[sourcery-ai]

Sorry @jonathanong, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[codspeed-hq]

Merging this PR will not alter performance

✅ 54 untouched benchmarks
⏩ 4 skipped benchmarks¹

---

_{Comparing codex/concurrency-queue (a32534a) with main (e095d99)}

Footnotes

1. 4 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩