[ui] Perform common job tasks with keyboard shortcuts

[philrenaud]

Traversal has been a strong-suit of keyboard navigation for long enough that I feel confident in its behaviour in the Nomad UI.

Now, this PR adds some basic action-running for jobs.

From the jobs index:

• run a new job with r u n

From a job page:

• exec with e x e c
• stop with s t o p
• purge with p u r g e
• start with s t a r t

[philrenaud]

Added this so that the letter n (from having typed run) doesn't show up in the job template editor box (keyboard service eagerly performs a task on keydown, but typing waits for keyup)

[github-actions]

Ember Asset Size action

As of ba6f522

Files that got Bigger 🚨:

File	raw	gzip
nomad-ui.js	+1.55 kB	+316 B

Files that stayed the same size 🤷‍:

File	raw	gzip
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

	main	ba6f522	change
passes	1485	1485	0
failures	0	0	0
flaky	0	0	0
duration	10m 55s 187ms	10m 57s 014ms	+01s 827ms

[lgfa29]

I think the label is the main thing that needs to be fixed (though I'm not sure what's the impact of having them wrong).

As for the confirmation I would gather a second opinion. My spidey-sense makes me worry a little about them in production.

(Also don't forget a changelog entry and the backport label 🙂)

[lgfa29]

It's a pretty long shortcut, but I'm kind of wary about the potential for unintended destructive operations here. Would it be possible to still have the confirmation pop-up? Keyboard shortcuts make things quick but sometimes it's good to slow down and double-check you are in the right namespace or something like that 😅

[philrenaud]

I've been giving this some thought. A couple things:

• Our two-step buttons are probably not a convention that we're going to continue with in the near future; Helios indicates that we should either use modals to warn, or toast/modals to make undoing easy. Once we start using modals, adding them to a queue of keyboard shortcut actions will be possible, but still not an ideal flow. As it stands now, the visual effect probably wouldn't be enough to make the user notice and they might have assumed the purge command went through without noticing otherwise.
• The act of typing the full word is a preeeeeetty deliberate action - something much harder to do than accidentally mouse-clicking or tab+entering on the button while enroute to do something else on the page.

As such, I think I'd like to move forward with this change. I am worried about the "double-checking you're in the right namespace" problem as well but the benefit here seems to outweigh the potential cost.

[ChaiWithJai]

There's one typo that should be fixed before you merge this.