Map service compatibility: WMS/WMTS + MapServer tile endpoint

[mikemcdougall]

Summary

Add map service compatibility endpoints for cached tiles and common standards interop:

• MapServer tile endpoint parity
• WMS endpoint support
• WMTS endpoint support
• tileInfo metadata exposure where applicable

Context

Current matrix lists these as not implemented:

• .../MapServer/tile/{z}/{y}/{x}
• .../MapServer/WMTS
• .../MapServer/WMS
• tileInfo in MapServer metadata

Reference: docs/user/map-server-matrix.md.

Scope

• Implement GET /rest/services/{serviceId}/MapServer/tile/{z}/{y}/{x}.
• Implement GET /rest/services/{serviceId}/MapServer/WMTS.
• Implement GET /rest/services/{serviceId}/MapServer/WMS.
• Populate tileInfo in service metadata when tile routes are enabled.
• Ensure response headers/content types align with expected client behavior.

Tasks

• Decide compatibility mode: direct generation vs cached pipeline backed by existing tiles stack.
• Implement endpoint handlers and parameter validation.
• Add EndpointRegistry entries + integration tests.
• Add interop tests against representative clients (MapLibre/QGIS/ArcGIS where feasible).
• Update docs/user/map-server-matrix.md and API examples.

Acceptance Criteria

• Endpoints return valid responses for standard test requests.
• MapServer metadata advertises tile capability consistently.
• Coverage/docs updated and tests passing.

Notes

Leverage existing OGC Tiles + MVT internals where possible to avoid duplicate tile generation logic.