Remove ginkgo v1 from operator build base

What does this MR do and why?

With gitlab-org/cloud-native/gitlab-operator#411 (closed), the operator migrated to ginkgo v2 (see: gitlab-org/cloud-native/gitlab-operator!574 (merged) and !634 (merged)). The build image provided both ginkgo v1 and v2 for MR pipelines that dont have the ginkgo v2 changes.

Active MRs now have the ginkgo v2 changes and/or use merge result pipelines, allowing the v1 CLI to be removed from the build image.

Past Operator releases (using ginkgo v1) are using the gitlab-build-images:gitlab-operator-build-base image which remains untouched, preventing failure of CI pipelines during patch releases.

Closes gitlab-org/cloud-native/gitlab-operator#411 (closed)

Checklist

• (If applicable) Add patches if required for upgrading Ruby version in https://gitlab.com/gitlab-org/gitlab-build-images/-/tree/master/patches/ruby.
  • not applicable