refactor: split operations() catalog builder by capability group

[github-actions]

What was complex

operations() in src/ado_proxy/catalog.rs was a single 391-line function (Clippy too_many_lines, 391/100) that built the entire flat Vec<Operation> catalog for every capability (discovery, core, repos, pipelines, boards) inline in one vec![...] literal.

What changed

Split the function into five smaller helpers, one per capability group, each returning its own Vec<Operation>:

• discovery_operations() — service-topology OPTIONS probes, resource-area discovery, connection data
• core_operations() — project lookup/validation
• repos_operations() — repository metadata, refs, items, commits, pull requests
• pipelines_operations() — build/release definitions, builds, timelines, pipeline runs
• boards_operations() — work item lookup, comments, updates, revisions

operations() now just concatenates the five helper outputs in the same order as before, so the returned Vec<Operation> is byte-for-byte identical to the pre-refactor version.

Behavior

No public API or observable behavior change — same operation list, same order, same Operation values.

Verification

• cargo test --bin ado-aw — all 3229 tests pass (0 failed, 1 pre-existing ignored)
• cargo clippy --all-targets --all-features — clean (one pre-existing, unrelated warning in create_work_item.rs)
• Cognitive-complexity re-check (-W clippy::too_many_lines) on src/ado_proxy/catalog.rs: max reported complexity dropped from 391/100 to 148/100 across the split functions.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• spsprodeus21.vssps.visualstudio.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "spsprodeus21.vssps.visualstudio.com"

See Network Configuration for more information.

Generated by Cyclomatic Complexity Reducer · auto · 107.3 AIC · ⌖ 9.38 AIC · ⊞ 11.4K · ◷

[azure-pipelines]

Azure Pipelines:
2 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[jamesadevine]

Closing as a duplicate of #2025. The executable catalog split is the same, while #2025 has the more accurate description.