test: add e2e pagination scenario for event-gateway backend clusters

[Copilot]

• Create test/e2e/scenarios/event-gateway/backend-cluster-pagination/testdata/egw-bc-pagination.yaml with 1 event gateway and 11 backend clusters
• Create test/e2e/scenarios/event-gateway/backend-cluster-pagination/scenario.yaml with reset, apply, paginated-get, and cleanup steps
• Add 002-delete-cleanup step using delete -f --auto-approve to clean up the 12 created resources
• Fix delete cleanup assertion to use "total_changes > \0`": true` (matching the pattern used in other event-gateway scenarios) instead of hard-coded counts that caused assertion mismatch failures

[rspurgeon]

@copilot add a cleanup (delete -f) step like was added to many scenarios in #871

[Copilot]

@copilot add a cleanup (delete -f) step like was added to many scenarios in #871

Added in commit 1b3769b. The new 002-delete-cleanup step runs delete -f egw-bc-pagination.yaml --auto-approve and asserts all 12 resources are deleted successfully.

[Copilot]

Pull request overview

Adds a new E2E scenario to validate paginated listing behavior for Event Gateway backend clusters, ensuring the CLI properly traverses multiple pages and includes cleanup.

Changes:

• Added declarative test data defining 1 Event Gateway and 11 backend clusters.
• Added an E2E scenario that resets the org, applies resources, performs a paginated get, and deletes created resources.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
test/e2e/scenarios/event-gateway/backend-cluster-pagination/testdata/egw-bc-pagination.yaml	Declarative config to create one gateway with enough backend clusters to force pagination.
test/e2e/scenarios/event-gateway/backend-cluster-pagination/scenario.yaml	New E2E workflow to apply, validate pagination via HTTP dumps, and cleanup via delete -f.

[rspurgeon]

@copilot review the test failure

    scenarios_test.go:77: scenario failed: 002-delete-cleanup/002-000-delete/assert-000: assertion mismatch; see /home/runner/work/kongctl/kongctl/.e2e-artifacts/24896344479-kongctl-acceptance-4/20260424-150501/tests/Test_Scenarios_test_e2e_scenarios_event-gateway_backend-cluster-pagination_scenario.yaml/steps/002-delete-cleanup/commands/002-000-delete/assertions/assert-000

workflow run 1619

[Copilot]

@copilot review the test failure

    scenarios_test.go:77: scenario failed: 002-delete-cleanup/002-000-delete/assert-000: assertion mismatch; see /home/runner/work/kongctl/kongctl/.e2e-artifact...

The assertion total_changes: 12 was too rigid — the actual delete plan count differed at runtime. Fixed in commit 0aef3af by switching to "total_changes > \0`": trueand adding aplan.metadata.mode: deletecheck, matching the pattern used in the other event-gateway delete cleanup steps (e.g.sync-workflow/scenario.yaml`).