Report actual status when running Debug command for component

[dgolovin]

In relation to #2229. There is no way to understand what has failed. Debug command goes through three steps:

• pushing component in debug mode
• running debug port-forward and capture local port from port mapping printed into standard output
• starting nodejs debugger usin localhost:port, where port is identified on step 2

All those steps should be visible in notification with progress, so we can identify where exactly debug command failed.

[xkwangcn]

Thank you. About the debug feature from windows remote to Z cluster, I can help to debug the reason.

[dgolovin]

@xkwangcn thanks! Let's continue in #2229.