chore: integ test workflows are reproducible

[nstng]

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

Summary

NOTE: The reasoning for this change might be subjective! If you have a strong opinion to not do this change, then please comment on this issue.

The integ tests workflows (make and bazel) are doing an apt dist-upgrade on the magma dev VM ...

• inconsistent: this is only happening on the magma vm - not on magma_test or magma_trfserver (yes, the magma vm is here more relevant, but this is still inconsistent)
• not reproducible: this can make the tests less reproducible as different versions (packages and kernel) might influence results
• runtime: after a fresh pre-burn image is released this step is not doing much - after some time it takes a couple of minutes
  • -> we should aim for more frequent releases of pre-burn images

Test Plan

Make sure the tests still run without a dist-upgrade - runs on fork:

• lte integ tests: https://github.com/nstng/magma/actions/runs/3196934901
  • -> green
• bazel lte integ tests: https://github.com/nstng/magma/actions/runs/3196931308
  • -> failure of one tests - looks like a flaky test failure not related to this change

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]

feg-workflow

    2 files  203 suites   39s ⏱️
374 tests 374 ✔️ 0 💤 0 ❌
388 runs  388 ✔️ 0 💤 0 ❌

Results for commit 6aa1d5c.

[github-actions]

dp-workflow

14 tests   14 ✔️  2m 8s ⏱️
  1 suites    0 💤
  1 files      0 ❌

Results for commit 6aa1d5c.

[github-actions]

agw-workflow

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

Results for commit 6aa1d5c.