Add initial maverick configuration ui

[SamuelDudley]

• interface for maverick commands, start, stop, etc...
• interface to view service status
• interface to view and edit config files

[SamuelDudley]

How vscode handles configuration from a form perspective (which in the background is a json file)

[SamuelDudley]

Basic interface to view and edit configuration files is complete. Working on a UI for commands and system processes now.

[SamuelDudley]

https://github.com/xtermjs/xterm.js
Use terminal for maverick command feedback

[fnoop]

ooh xterm.js is a nice idea!

[SamuelDudley]

added the -web component of xterm.js dc27bb1

just hacked it in, but we can link this to -api for two outcomes:

1. Show realtime terminal output from the process runner (e.g. maverick configure)
   https://github.com/goodrobots/maverick-api/blob/7ef29f4283e618320710c825c3b21513ab62bb96/maverick_api/modules/base/util/process_runner.py

2. Allow the user to interact with the terminal from the webui using the process runner

[SamuelDudley]

https://github.com/wavesoft/local-echo/blob/master/lib/LocalEchoController.js

[fnoop]

awesome! would be great to have a mav terminal built in

[SamuelDudley]

The terminal support was working (ish) prior to the API refactor in -web. It would be nice to get that back as it saves a user from needing to SSH in for basic stuff.

[fnoop]

'Commands' re-instated. If it's going to be a full terminal (which is great), should probably be renamed to Console/Terminal.
Console works-ish, restricted to a particular directory and the output is a bit hoky. If we can get it working better will be fantastic to have.

[SamuelDudley]

Yeah, the plan is to have the full terminal working. -api is okay at this stage, the remaining work is in the -web component.

Ill raise some specific issues for it to keep track of what needs to change for it to function properly.