Move public APIs under api/<api-name>/v1. - #2996

…before the step changes anything (#132)

On a v1.0.0-rc.1 cluster the optional Filestore step failed at "Apply
Kustomize overlay": upstream's overlay writes its CSIDriverConfig against
ate.dev/v1alpha1, and agent-substrate/substrate#2996 moved the CRDs to
ate.dev/v1, which is all the cluster serves. By then deploy.sh had granted
roles/file.editor and bound Workload Identity, the step had turned off the
managed Filestore addon, and the apply had created the namespace,
Deployment and DaemonSet (node pods crash-looping) without the config. The
wizard's [s] moved on and both summaries said "filestore skipped".

The script now clones the overlay first and reads the apiVersion from its
csi_driver_config.yaml, compares it with the served versions of
csidriverconfigs.ate.dev, and fails there — naming both versions, saying
nothing was changed, and pointing at kubernetes-sigs/gcp-filestore-csi-
driver#1416 — before any gcloud call. A cluster without the CRD fails the
same way. The clone stays at HEAD rather than a pin: no revision of the
overlay serves v1 yet, so a pin would only fix the failure in place, while
HEAD picks up the upstream fix when it lands and the check keeps the step
honest until then. The checklist rows follow the new order, and the addon
row lights on "nothing to disable" instead of staying unlit on a cluster
without the managed driver.

A run that fails and is skipped from the failure is recorded
(FilestoreCSIFailed) and reported as "failed" by the completion panel and
the exit summary, which points at the namespace a partial apply leaves
behind; a later run that succeeds clears it. The README row says what the
step checks and that it stops on this pin.

Tests run the check as written against a fake kubectl (v1alpha1 against
v1 fails with the full message, v1 passes, both served passes, no CRD
fails), assert the script's ordering with no gcloud ahead of the check,
cover the checklist order and the failed-check stop, and drive the
Filestore screen through a failure, the skip, and a successful rerun.

Fixes #114

Co-authored-by: Aditya Shantanu <[email protected]>