test(ogc): bdms-923 add Sprint 1 cleanup feature spec for OGC

[ksmuczynski]

Why

This PR addresses the following problem / context:

• BDMS-923 calls for a behavior spec capturing Sprint 1 of the OGC feature layer cleanup so expected behavior is documented before implementation lands.
• The OGC layers need a single source of truth for what Sprint 1 covers (exposure filters, naming, configuration) versus what's deferred, so reviewers, testers, and follow-up sprints can plan against the same scope.
• Helps ensure scenarios are properly categorized for efficient tracking and execution.

How

Implementation summary - the following was changed / added / removed:

• Introduced a new BDD feature file capturing the Sprint 1 cleanup scenarios.
• Tagged scenarios with relevant metadata like concern, scope, priority, and action item.

Notes

Any special considerations, workarounds, or follow-up work to note?

• Spec-only PR — no step definitions or production code changes yet. Scenarios are intentionally pending until the Sprint 1 implementation work lands.
• A2 is @wip: terms_of_service and contact_name still need confirming with the technical lead before that scenario can run in CI
• A22 ADR: needs to be written before the two remaining A22 scenarios are meaningful — see comment in the file.
• other_things ordering: A1 S3 and all three A13 scenarios include other_things because A1 still needs to patch its view; comments in the file flag that these should run before A18 is applied.
• A4 count may drift: 322 is the audit snapshot — if the data changes before step definitions are written, this will need updating.
• A11 role name TBD: the Authentik role for /ogcapi-internal access is part of A11 itself and doesn't exist yet; "public-viewer" and "required role" references in A11 S2–S4 should be updated once it's provisioned.

[chasetmartin]

Looks good! If you run into issues testing against exact feature or entity counts you may need to adjust a few clauses, but I would just roll with it as you work through them.