Use alternative Ginkgo invocation

This prevents warnings of version mismatch between installed ginkgo CLI
and ginkgo version used in tests.

Author: Zerpet

Makefile

@@ -65,9 +65,11 @@ unit-tests::vuln
 unit-tests::manifests
 unit-tests::just-unit-tests ## Run unit tests
 
+GINKGO ?= go run github.com/onsi/ginkgo/v2/ginkgo
+
 .PHONY: just-unit-tests
 just-unit-tests:
-	ginkgo -r --randomize-all api/ internal/ pkg/
+	$(GINKGO) -r --randomize-all api/ internal/ pkg/
 
 .PHONY: integration-tests
 integration-tests::install-tools
@@ -81,7 +83,7 @@ integration-tests::just-integration-tests ## Run integration tests
 
 .PHONY: just-integration-tests
 just-integration-tests:
-	ginkgo -r controllers/
+	$(GINKGO) -r controllers/
 
 manifests: install-tools ## Generate manifests e.g. CRD, RBAC etc.
 	controller-gen crd rbac:roleName=operator-role paths="./api/...;./controllers/..." output:crd:artifacts:config=config/crd/bases
@@ -232,7 +234,7 @@ cert-manager-rm:
 	kubectl delete -f https://github.com/cert-manager/cert-manager/releases/download/v$(CERT_MANAGER_VERSION)/cert-manager.yaml --ignore-not-found
 
 system-tests: install-tools ## Run end-to-end tests against Kubernetes cluster defined in ~/.kube/config
-	NAMESPACE="$(SYSTEM_TEST_NAMESPACE)" K8S_OPERATOR_NAMESPACE="$(K8S_OPERATOR_NAMESPACE)" ginkgo -nodes=3 --randomize-all -r system_tests/
+	NAMESPACE="$(SYSTEM_TEST_NAMESPACE)" K8S_OPERATOR_NAMESPACE="$(K8S_OPERATOR_NAMESPACE)" $(GINKGO) -nodes=3 --randomize-all -r system_tests/
 
 kubectl-plugin-tests: ## Run kubectl-rabbitmq tests
 	@echo "running kubectl plugin tests"