chore(ci): Add option to store bazel profile data to bazel.yml workflow

[LKreutzer]

Signed-off-by: Lars Kreutzer lars.kreutzer@tngtech.com

Summary

• Resolves Reduce amount of stored Bazel profile data #14168
• Bazel profile data is not stored per default
• If data should be stored in manual workflow runs the box needs to be ticked
  

Test Plan

• Workflow run without option ticked
• See also run on this PR

Additional Information

• Boolean inputs are strings and not booleans

  • See Boolean inputs are not actually booleans actions/runner#1483

• 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 1ac5bb3.

[Neudrino]

By the way, ${{ }} are not necessary in if:. But neither are they wrong.