Backport of [ui] Add "stopped" as a valid status on jobs index/job detail into release/1.8.x

[hc-github-team-nomad-core]

Backport

This PR is auto-generated from #23328 to be assessed for backporting due to the inclusion of the label backport/1.8.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@philrenaud
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/nomad/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

Our recent changes to how we label jobs in the UI considers any job "failed" if none of its expected allocations are running or pending, and it's not in active deployment.

This is coincidentally both true for jobs that failed because a user clicked the "stop" button, and also for jobs that failed because of the universe conspiring against us generally.

Luckily, jobs already had a nice Stop boolean to indicate the manual, deliberate stopping of a job (until it gets garbage collected, and provided it didn't have a "purge" flag passed in).

This PR observes that boolean and displays a new "Stopped" status in the UI in two places:

resolves #22101

---

Overview of commits

• 8e589a9

[hashicorp-cla-app]

All committers have signed the CLA.

[github-actions]

Ember Test Audit comparison

	release/1.8.x	9488d91	change
passes	1562	1563	+1
failures	2	2	0
flaky	0	0	0
duration	000ms	000ms	-000ms

[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.