ci: Speed Up Code Coverage Github Actions Jobs

[bnussman-akamai]

Description 📝

Slightly speeds up our new code coverage Github Actions jobs by not building a production Cloud Manager bundle 🏎️

We should see an improvement of about 30-60 seconds ⏲️ Nothing groundbreaking, but slightly better.

How to test 🧪

• Check the GitHub Actions below this PR and verify that the Code Coverage jobs work as expected

As an Author I have considered 🤔

• 👀 Doing a self review
• ❔ Our contribution guidelines
• 🤏 Splitting feature into small PRs
• ➕ Adding a changeset
• 🧪 Providing/Improving test coverage
• 🔐 Removing all sensitive information from the code and PR description
• 🚩 Using a feature flag to protect the release
• 👣 Providing comprehensive reproduction steps
• 📑 Providing or updating our documentation
• 🕛 Scheduling a pair reviewing session
• 📱 Providing mobile support
• ♿ Providing accessibility support

[github-actions]

Coverage Report: ✅
Base Coverage: 77.15%
Current Coverage: 77.18%

[abailly-akamai]

This works! small improvement, wondering what prompted you to want to improve the speed here. This action is non blocking and we usually want to wait for the e2e suite to finish before merging anyway, which takes far more time.

If we really want to improve speed here, we could upload the base coverage pct to another bucket on every merge to develop and download it on each run so we don't have to run the unit suite on the ref branch. Would cut the job time by almost half but unless I am missing a particular use case I dunno if worth the effort?

[bnussman-akamai]

No significant reason, I just noticed we could skip the Cloud Manager build when I did #9973

If we really want to improve speed here, we could upload the base coverage pct to another bucket on every merge to develop and download it on each run so we don't have to run the unit suite on the ref branch. Would cut the job time by almost half but unless I am missing a particular use case I dunno if worth the effort?

I thought about this, but I appreciate the simplicity of how it is now and the fact that it can dynamically get the coverage of the base_ref

[mjac0bs]

Confirmed the action works to produce the coverage report and we see a small increase in speed:

Action run on this branch:

Action run on another PR branch: