[vvoytovych]

The required check, ci / Build and test, and the Tests workflow both run the whole unit and envtest suite on every pull request, so each pull request runs it twice (#837). CI now also runs on pushes to release/**, as Tests does, and takes the concurrency group that the other workflows share, so Tests goes. Every other step of Tests already runs in another check, or checks nothing. make test stays for local use.

Where each step of Tests runs now

step	where
make manifests generate	Verify Generated Files, which fails on any diff
go vet, go fmt	Lint: golangci-lint's govet, gofmt and goimports
the build	CI: ci-basic's Go step runs go build ./...
the unit and envtest suite	CI
go mod tidy, go fmt as a step	nowhere: both rewrite files and never fail
-coverprofile cover.out	nowhere: nothing reads it

Corner cases

case	what happens	proof
A push to a release branch	CI runs the suite, as Tests did	the same branch filter as Lint and Verify Generated Files, which ran on release/v0.34's last push
A newer push to a pull request	The older CI run is cancelled	the group the other workflows use
A push to main or a release branch	Its run is never cancelled	the group is the run's own id there
The required check	Keeps its name, ci / Build and test	the job is unchanged

Test plan

• actionlint passes on every workflow, and nothing else in the repository names test.yml or the Tests workflow.
• This pull request's checks: CI runs, Tests does not.
• After the merge, the next push to a release branch runs CI.

Refs #837

[ecv]

Approve.

Deleting test.yml removes a second run of the same suite: ci.yaml's ci / Build and test already runs the unit and envtest packages (go test $(go list ./... | grep -v /e2e) -timeout 25m under setup-envtest), and it is the only check the required-ci ruleset requires, so no required check disappears. The 26-minute duplicate goes, and both checks passed at the head.

• ci.yaml gains release/** pushes and the same cancel-in-progress concurrency test.yml had, so release branches keep their test run.
• make test also ran manifests generate fmt vet. Generated files are still covered by Verify Generated Files, and vet and fmt by the lint workflow, so nothing that gated before stops gating.

Follow-ups:

• ci.yaml pins envtest to Kubernetes 1.31.0 while make test uses ENVTEST_K8S_VERSION; keep the two in step, or have CI call the Makefile target.

[vvoytovych]

Thanks, ecv. Agreed, and the two copies have already drifted: the Makefile installs setup-envtest from release-0.19, and ci.yaml from a release-0.25 commit. After this PR and #848 merge, I'll open a PR in which CI calls one Makefile target, so the Kubernetes and setup-envtest versions live in one place.