[ui] When a job is deleted in the background, wait until redirect before cache unload

[philrenaud]

This prevents an issue where, still on the job page, the cache-removed job would have trouble accessing properties and relationships of its now-removed Ember Data object.

Resolves #23410

[github-actions]

Ember Test Audit comparison

	main	16fb206	change
passes	1573	1573	0
failures	0	0	0
flaky	0	0	0
duration	11m 35s 957ms	11m 27s 219ms	-08s 738ms

[pkazmierczak]

LGTM!

[tgross]

Seems like a reasonable change, but it looks like it broke a related test.

[philrenaud]

Broken test is now fixed; was related to a core piece of Ember's transition-handling where a transition can happen at both a high level (the application route has one) and a low level (the redirect we're patching up here) and the former is left "floating". A try/catch block prevents the uncaught failure.

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