test(e2e): strengthen post-sync field assertions in control-plane sync scenario

[Copilot]

The 002-sync-with-delete sync step only verified existence of kongctl-e2e-cp-2 by name after sync, leaving description and cluster_type unasserted — a regression in either field would pass undetected.

Changes

• 001-002-verify-post-sync — extended the existing list-based assertions for kongctl-e2e-cp-2 to also assert description and config.cluster_type, using JMESPath selects on the same list response:

- select: "[?name=='kongctl-e2e-cp-2'] | [0]"
  expect:
    fields:
      name: "kongctl-e2e-cp-2"
      description: "Second Test Control Plane for E2E testing via kongctl"
- select: "[?name=='kongctl-e2e-cp-2'] | [0].config.cluster_type"
  expect:
    fields:
      "@": "CLUSTER_TYPE_CONTROL_PLANE"

No overlay or testdata changes — pure assertion additions in the existing verification step, consistent with the apply scenario's 002-001-verify-fields pattern.

[Copilot]

Pull request overview

This PR strengthens the E2E “control-plane sync” scenario by asserting additional fields after the sync-with-delete step, reducing the chance of regressions slipping through when the control plane still exists but key fields are wrong.

Changes:

• Extend the existing post-sync list assertion for kongctl-e2e-cp-2 to also validate description.
• Add a new post-sync “get by name” verification command to assert description and config.cluster_type from the single-resource JSON output.

[rspurgeon]

@copilot this scenario change adds a second kongctl get command to check the values of the same object. Instead, how about extending the assertions in the existing 001-002-verify-post-sync step instead of authoring an entirely new step with a redundant 'kongctl get' to retrieve essentially the same data as the prior step.

[Copilot]

@copilot this scenario change adds a second kongctl get command to check the values of the same object. Instead, how about extending the assertions in the existing 001-002-verify-post-sync step instea...

Done in 534d533. Removed the separate 002-002-verify-created-fields step and consolidated config.cluster_type into the existing 001-002-verify-post-sync step using a JMESPath select on the same list response: [?name=='kongctl-e2e-cp-2'] | [0].config.cluster_type.