Add the kubectl plugin build task to the gke snippets dependencies

[fealebenpae]

Summary

The download_multi_cluster_binary function expends to find the multicluster binary on S3 using the current patch id. Adding a dependency on the build_kubectl_mongodb_plugin task to the multicluster code snippets tests ensures there is a multicluster binary at the expected path for the current patch.

Proof of Work

The multi cluster code snippet test tasks don't fail (at least not with a missing kubectl-mongodb error).

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.1 Release Notes

[MaciejKaras]

This makes sense for private snippets, but for public we should already have the kubectl_mongodb_plugin build and pushed to correct S3 path.

[m1kola]

@MaciejKaras I've noticed that our snippets job tries to pull dev S3 instead of staging, if we run the patch as per release guide:

evergreen patch -p mongodb-kubernetes -v public_gke_code_snippets,public_kind_code_snippets -t all -d "Release 1.6.1: public gke snippets" -u -f -y --browse

[MaciejKaras]

Well in fact it should try to pull the binary from the release bucket instead. We could either run the command with additional param --param BUILD_SCENARIO=release or make sure we set proper build_scenario in the public_gke_code_snippets variant somehow. WDYT @viveksinghggits ?

Also I'm really close to making code snippets part of automated release workflow, so we won't need to fix it soon.

[viveksinghggits]

I was also in favor of making sure proper build_scenario gets set in the public_gke_code_snippets. That would also make things more clear that we are using build scenario in the script/variant.

[m1kola]

Let's put a hold on this for now. I think we are just trying to pull the binary from the wrong place.

[m1kola]

@MaciejKaras I've noticed that our snippets job tries to pull dev S3 instead of staging, if we run the patch as per release guide:

evergreen patch -p mongodb-kubernetes -v public_gke_code_snippets,public_kind_code_snippets -t all -d "Release 1.6.1: public gke snippets" -u -f -y --browse