fix: bazel base uses same folly version as magma vm

[nstng]

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

Summary

This PR re-applies #13743 (reverted in #13753). This time #13757 was applied before so that bazel workflows still run on the bazel base image before this change.

A follow-up PR will be created where the cache key in bazel workflows will be changed and the latest image is used again. By this, the cache failures that caused the revert should be prevented.

Test Plan

• see that https://github.com/magma/magma/runs/8231653751?check_suite_focus=true was successful

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 3d7a81a.