UI: Fix recommendation test to ensure CPU exists

[backspace]

This fixes a flaky test, as seen in this failure mentioned here.

One part of the test involves toggling off all memory recommendations
and then accepting, but it’s not possible to accept when there are
no CPU recommendations to begin with, which can happen because
there’s a 10% chance of not creating a corresponding recommendation
in the task factory. Since two tasks are created for this module, it’s
only a 1% chance of no CPU task, but that means 1% flakiness!

I confirmed this was the problem by using faker-seed=69400 and
await this.pauseTest():

With this mitigation in place, the same seed has a CPU recommendation and the
summary can therefore still be accepted with memory toggled off:

Another approach would be to have a flag to remove randomness when
creating recommendations, but this one-time intervention seems preferable
to having to pass that down through the factories, to me 🤔

[github-actions]

Ember Asset Size action

As of 5c71131

Files that stayed the same size 🤷‍:

File	raw	gzip
nomad-ui.js	0 B	0 B
vendor.js	0 B	0 B
nomad-ui.css	0 B	0 B
vendor.css	0 B	0 B

[github-actions]

Ember Test Audit comparison

	master	5c71131	change
passes	1555	1555	0
failures	0	0	0
flaky	0	0	0
duration	8m 00s 595ms	7m 27s 839ms	-32s 756ms

[DingoEatingFuzz]

I like this intervention! The test remains true to its intent and factories don't get any extra spaghetti.

[github-actions]

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.