test: migrate remaining resource commands and remove legacy mock-command coverage

[guoqqqi]

Refs #19

Goal

Complete the remaining command-family Ginkgo E2E migration after the first core-resource batch.

Current Boundary

• Keep existing mock Admin API unit tests for now.
• Do not add new mocked Admin API command tests.
• Add Ginkgo E2E coverage against a real APISIX Admin API.
• Prefer CLI lifecycle assertions: create, update, delete, list/export, and get.
• Do not require real proxy/data-plane validation by default.
• Legacy mock-test removal is deferred to a separate future decision.

Remaining Areas Covered

• consumer / credential / consumer-group
• ssl / stream-route / proto / secret / plugin-metadata
• debug / completion / version / extension / context where applicable

Completed Work

This migration has been implemented through merged PRs:

• test: migrate config and group commands to ginkgo e2e #25 config and group command Ginkgo E2E
• test: add consumer credential ginkgo e2e #27 consumer and credential Ginkgo E2E
• test: add proto secret ginkgo e2e #28 proto and secret Ginkgo E2E
• test: add ssl stream route ginkgo e2e #29 ssl and stream-route Ginkgo E2E
• test: add utility command ginkgo e2e #30 utility command Ginkgo E2E
• test: add debug command ginkgo e2e #31 debug command Ginkgo E2E

Acceptance Criteria

• remaining command families have Ginkgo E2E coverage where useful
• resource behavior is asserted through CLI reads against real APISIX Admin API
• existing mock Admin API unit tests are preserved in this phase
• CI remains green and stable

[guoqqqi]

Completed under the updated boundary. The remaining command families now have Ginkgo E2E coverage through #25, #27, #28, #29, #30, and #31. Existing mock Admin API unit tests are intentionally retained for now; any removal should be handled as a separate future cleanup decision.