User-friendly startup and logging

[Terracom12]

Related to #214

Before the web interface, there needs to be a usable api for launching ros2 nodes. Also a simple way to startup the GUI itself. Changing the Makefile into a python script might be ideal; this would provide both cli tools and an api.

A few things this interface should be capable of doing:

• [ ] Setting log level (per-node) and redirecting logs
• [ ] Starting up arbitrary nodes and groups of nodes (i.e. for a specific mission)
• [ ] Multiplexing the output of each launch program into a terminal pane
  • Move away from Terminator for this, as its config options for this sort of workflow are rather terrible. Kitty is a decent alternative, but its not POSIX compliant and doesn't function well over ssh out of the box. Tmux with any arbitrary terminal would probably be ideal.
  • This also encompasses automatically sshing and attempting to run the specified programs there
• [ ] Thorough error handling. Anyone (non-programming members) might be using the cli before the gui gets integrated, so this is essential.
  • A few example errors/warnings that should be caught, and automatically solved if possible: missing or outdated repository, device not found (ssh), required package not installed, etc.

[Terracom12]

This looks like a viable solution for a centralized launch system on ROS2 forums.

It's a little bit complex, and it seems like remote launching was a proposed feature in ROS2 a few years back, so we should look into whether they made any progress on implementing that.

[Terracom12]

This repo might prove helpful: https://github.com/paramiko/paramiko