Arvados

We want this to work the same as every other confirmation dialog. Assuming it does, I see no need for interface review, except maybe double-checking the actual text of the dialog. If something happens that means we can't follow that plan, let me know.

Changes at arvados|491b0ab06d03c763004029b13927f9d48e4d2f52 branch 23161-confirm-cancel-process
Tests developer-run-tests-services-workbench2: #1628

• All agreed upon points are implemented / addressed. Describe changes from pre-implementation design.
  • Cleaned up mapDispatch methods that were unused
  • Added confirmation dialog to cancel process - also added to context menu since that shows up in the toolbar and could also be accidentally clicked about as easily as the cancel button itself
  • Changed wording to avoid having both dialog buttons be "Cancel"
• Anything not implemented (discovered or discussed during work) has a follow-up story.
  • none
• Code is tested and passing, both automated and manual, what manual testing was done is described.
  • Adjusted to pass existing tests
• The tested code incorporates recent main branch changes.
  • yes ("Incorporates" = merged or rebased. "Recent" = 2-3 working days. The more active development on this component is, the more important it is to be based on recent main to avoid surprising test failures post-merge.)
• New or changed UI/UX has gotten feedback from stakeholders.
  • no significant change
• Documentation has been updated.
  • n/a
• Behaves appropriately at the intended scale (describe intended scale).
  • no change
• Considered backwards and forwards compatibility issues between client and server.
  • none
• Follows our coding standards and GUI style guidelines.
  • yes

LGTM