OGC API Features parity: PATCH + ids/properties/sortby support

[mikemcdougall]

Summary

Improve OGC API Features query/update parity by adding the most-used missing items endpoint capabilities:

• PATCH /ogc/features/collections/{collectionId}/items/{featureId}
• ids query parameter
• properties query parameter
• sortby query parameter

Context

Current coverage notes these as missing:

• PATCH for single item updates
• sortby, properties, ids query parameters

Reference: docs/user/specifications/ogc-api-features-coverage.md.

Scope

• Implement PATCH /ogc/features/collections/{collectionId}/items/{featureId} with partial update semantics.
• Implement ids filtering on items collection endpoint.
• Implement properties field projection on items collection endpoint.
• Implement sortby ordering with validation against queryables.
• Ensure compatibility with existing filters (bbox, datetime, filter) and pagination.

Tasks

• Extend OGC items request parsing/validation for ids, properties, sortby.
• Add patch model/handler logic and validation rules.
• Add endpoint registry + integration tests (required API surface coverage).
• Update coverage docs/examples.

Acceptance Criteria

• Endpoints/parameters behave consistently with documented OGC contract.
• Integration tests cover positive and validation/error scenarios.
• docs/user/specifications/ogc-api-features-coverage.md updated from "Not implemented"/"Partial" where applicable.

Notes

Keep MVP-focused behavior explicit (document unsupported edge cases rather than implicit fallback).

[mikemcdougall]

Implemented on branch feat/307-309-ogc-patch-geometry-ops in commit 6680ddc.\n\nShipped:\n- PATCH /ogc/features/collections/{collectionId}/items/{featureId} with merge semantics\n- ids/properties/sortby support on items query\n- integration coverage for new behaviors\n\nNote: documentation updates are being handled in a separate docs workstream.