BDD DSL: Wait for Gateway API routes

[sbaum1994]

Why

The local multi-cluster and EKS features repeat kubectl wait commands for Gateway API Accepted=True and ResolvedRefs=True. The route identities, namespaces, context, timeout, and required conditions are meaningful; JSONPath syntax is not.

Scope

Add a table-driven assertion that explicit Gateway API routes become accepted and resolved using an explicit Kubernetes context and timeout.

Acceptance criteria

• Add the step and table shape to the documented DSL catalog.
• Require route kind, name, and namespace for every row plus an explicit context and timeout.
• Support the route kinds already exercised by the suite, including HTTPRoute and GRPCRoute.
• Require both Accepted=True and ResolvedRefs=True without weakening existing checks.
• Report the failing route and condition without dumping the complete resource.
• Add focused command-construction, handler, interpolation, and failure tests.
• Migrate suitable route wait blocks in local multi-cluster and EKS features.
• Pass affected wiring tests and live feature tests.

Parent: #858