chore: cache key of bazel base and image tag are updated

[nstng]

Signed-off-by: Nils Semmelrock nils.semmelrock@tngtech.com

Summary

Closes #13818.

Last step of aligning folly in the vm and in the bazel base image. See https://github.com/magma/magma/wiki/Bazel-remote-caching#solving-breaking-changes-in-remote-caches for a detailed description.

Note: already filled caches from a local setup for bazel-base-image-sha-c4de1e5.

Test Plan

• read (and correct if necessary) https://github.com/magma/magma/wiki/Bazel-remote-caching#solving-breaking-changes-in-remote-caches
• see bazel jobs succeed in PR checks

Additional Information

• This change is backwards-breaking

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[github-actions]

dp-workflow

0 tests   0 ✔️  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 9bc29f3.

♻️ This comment has been updated with latest results.

[github-actions]

agw-workflow

615 tests   611 ✔️  4m 46s ⏱️
    2 suites      4 💤
    2 files        0 ❌

Results for commit 9bc29f3.

[vktng]

LGTM.

[nstng]

Set DONOTLAND for now - last time this change broke CI. This time I am confident that it will work, but I prefer to merge this next week in order to monitor it and react fast if something breaks.