chore(pipelined): devcontainer and bazel-base use needed depencies

[vktng]

Signed-off-by: Krisztián Varga krisztian.varga@tngtech.com

Summary

Add needed dependencies for devcontainer and bazel-base which are required by #12271

Test Plan

No docker build failures in CI. Tested locally with #12271.

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

[electronjoe]

Are the Hadolint findings in the PR useful?

[vktng]

Are the Hadolint findings in the PR useful?

They make sense, but we never used version pinning in these Dockerfile-s. If we want to use this, then we should do it in a separated technical debt task. The other issues were not introduced here, but are related to the changed lines (of course this is not an argument to not fix it, but this should again be done in a separate task for all occurences). Is this ok for you?

[nstng]

in pairing

[github-actions]

Unit Test Results

157 files  157 suites   2h 4m 59s ⏱️
307 tests 304 ✔️ 3 💤 0 ❌

Results for commit 53c4848.

♻️ This comment has been updated with latest results.