[CLOUDP-338093] Use goreleaser to build kubectl-mongodb plugin for dev/staging workflows

[viveksinghggits]

Summary

Per current implementation when we release the binary we build it via goreleaser but in our dev and staging workflows we used scripts/evergreen/build_multi_cluster_kubeconfig_creator.sh (which eventually run go build) to build the binary. We needed to change this to make sure that we are using the same mechanism to build the binary in dev/staging workflows that we use while releasing. In order to achieve that, this PR adds functionality to build the kubectl-mongodb plugin using goreleaser in dev/staging workflows.

As part of the new workflow, build_multi_cluster_binary evergreen function has been changed to run goreleaser build and upload the artifacts to a S3 location. After that the linux/amd64 distribution of the binary is downloaded locally at the path where tests image expects it.

Having the binary in the S3 bucket would eventually help us to just promote the binaries while the release process but we are not able to achieve that for now, because for dev/staging workflows we are not able to notarize the generated binaries.

After this PR, potentially we can even consider just getting rid of the script scripts/evergreen/build_multi_cluster_kubeconfig_creator.sh.

Proof of Work

Run the local patch using

evergreen patch --path .evergreen.yml -p mongodb-kubernetes -v init_test_run -t build_test_image -f -y -u --browse -d "Testing build of kubectl plugin using build scenario"

and make sure that test image is built successfully and the goreleaser artifacts are uploaded to the S3 bucket (mongodb-kubernetes-dev) correctly.

CI passing on this PR also proves that the binary is successfully built and copied to the test image.

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you added changelog file?
  • use skip-changelog label if not needed
  • refer to Changelog files and Release Notes section in CONTRIBUTING.md for more details

[github-actions]

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.6.0 Release Notes

New Features

• MongoDBCommunity: Added support to configure custom cluster domain via newly introduced spec.clusterDomain resource field. If spec.clusterDomain is not set, environment variable CLUSTER_DOMAIN is used as cluster domain. If the environment variable CLUSTER_DOMAIN is also not set, operator falls back to cluster.local as default cluster domain.
• Helm Chart: Introduced two new helm fields operator.podSecurityContext and operator.securityContext that can be used to configure securityContext for Operator deployment through Helm Chart.

Bug Fixes

• Fixed parsing of the customEnvVars Helm value when values contain = characters.

[lsierant]

It's LGTM generally, but I've left one blocking comment.

[lsierant]

LGTM!

[viveksinghggits]

Hi @MaciejKaras,
I have rebased this with master, can you please have a quick look again so that I can merge this now.