Hooking up the skeleton of the pause action
Wiring up the approve/reject logic
Added the parameter handling
Hooking up initial UI
Crossing Ts and dotting Is.
Using a different UI if the pause is settled
Making it a ModelObject to participate in the breadcrumb
Changing the mind. Let's have PauseAction only list ongoing pauses.

... because FlowNode is a better to place to record historical outcome, and this makes it easier to deal with pauses in a loop, etc.
Fixing up the terminology.

This is input, and approval is just one use case.
If there's no active pause, hide from the UI
Avoid using [a-z] as the first letter of pause to disambiguate InputAction views vs actions
If #execution fails to load, isBuilding() shouldn't be reporting true.
Merge commit '1ef92e4485a03fcc9bec5e9bc37e474379a6d207'