Pause / Resume for docker boot dash malfunctions

[kdvolder]

Describe the bug

When we 'resume' a paused docker process via the context menu on the top-level node (i.e. the node representing the app rather than the container) it misbehaves:

• If container is running in 'normal' mode (i.e. not 'debug' mode) and then paused...
  => the app node neverteless shows it as 'REsume debugging)'
  => invoking that function actually does connect the debugger, but it doesn't actually 'resume' but rather starts a new / separate container instead.

• if container is running in debug and then paused...
  => the menu correctly shows 'resume debugging'
  => Selecting the menu doesn't actually do anything however.

To Reproduce

• Deploy a new boot app to docker
• pause it
• try resuming it

You can observe all the above described behaviors.

[kdvolder]

Debugged a bit. A one line fix, seems like it was a copy-pasting error. The logic for not making it visible on app nodes was only present in the 'Resume (Running)' action but it really should apply to both 'Resume (Running)' and 'Resume (debugging)'. The original intent when this was implemented seems to have been to only have the menu on nodes that can be direclty 'paused' (i.e. only nodes that have 'pause' will also have a 'resume (XXX)'.

So it was a simpe one line code fix.