"Deploy" removed, Register Rework

[bigcat88]

PR should not break anything, for old parts added a workarounds, that we will remove in a month when all ExApps will publish their updates.

Changes:

• UI now use the same algorithm/code for ExApp register & update as the CLI commands.
• Deprecated "deploy" command, now register commands performs deploy.

Refactoring:

• Removed internal DispatchInit command, as from CLI we already can do it without spawning additional process.
• Removed hack(status['active']) when we have some half-enabled state of ExApp when it is not enabled, but already can call APIs, now ExApp enables before calling /init
• Made code more consistent in many place.

OTHER CHANGES FOR DEVS:

• For --json-info parameter in occ register command keys renamed: "appid" -> "id", "system_app" -> "system"

  Old naming is still supported but will be removed in future, in such way we make consistent parameters between info.xml and --json-info.

---

Related: #219
AppAPI will perform deploy & registration in a background and issue should be fixed

[bigcat88]

Updated docs

[bigcat88]

If an error occurs during "Registration" when retrieving an image, the ExApp will be unregistered. The frontend continues to spam about errors, although it is enough to say once that there was an error.
And if ExApp is present then display the info from status['error'] or if ExApp is missing then just: "check logs" string.

[bigcat88]

Second/third issue(s):

When I press "Deploy and Enable" I see that progress go and I made a page refresh(F5).
Button "Remove" appeared near the progress what I think is should not happen?

Also after that UI stopped on ending progress and ExAPP in UI do not reach "Enabled" state.