Expose advanced Project view configuration after API parity ships

[zwick]

Problem

The Projects tools do not expose advanced Project view configuration such as visible field ordering, custom grouping, vertical grouping/swimlanes, sorting, slicing, or roadmap settings.

The MCP shape should follow generally available public API contracts rather than duplicate service-internal storage formats.

Scope

After stable public APIs support these controls:

• Extend the existing Projects tool surface with the available typed configuration controls.
• Reuse public API input, validation, and clearing semantics.
• Keep tool descriptions and response shapes concise.
• Add schema/token-cost measurement and targeted evals for table, board/swimlane, and roadmap setup.
• Validate complete Project-view setup against the real GitHub API.

Non-goals

• Designing the underlying API contract in this repository.
• Depending on preview headers or undocumented API behavior.

Acceptance criteria

• Agent tooling exposes each generally available advanced configuration capability with typed parameters.
• Evals distinguish model failures from tool/API failures.
• Live API validation covers useful table, grouped board/swimlane, and roadmap views without manual configuration.