Rspec:coverage should not wait for memory-on-boot

Context

I noticed that sometimes predictive pipelines would have the memory-on-boot on their critical path, because it is declared as a needs: for the rspec-coverage job (memory-on-boot takes more than 10 minutes to run).

memory-on-boot doesn't need to be in the needs list of rspec:coverage, because:

• the memory-on-boot job produces a artifact:reports:metrics report.
• the rspec:coverage job produces a artifacts:reports:coverage_report report

Both reports are used by different product features in the MR, and both reports will be picked up independently.

What does this MR do and why?

Ensures that rspec:coverage does not depend on the memory-on-boot job.

Does it work?

1. The metrics report is still present in the MR:

2. rspec:coverage does not wait for memory-on-boot anymore 🎉

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.