Separate code from data

[MichaelCurrin]

Major upgrade in functionality, to be handled by several issues but possibly one in one PR (since changes are all large and work together and backwards behavior can be lost) or series of PRs.

• Make unicron installable as a python file (with venv in bin path or install globally as long as dev dependencies are left out)
• Use ~/.unicron for output and run data
• Use config file there too. Editable through IDE or maybe through terminal like crontab -e and validate as YAML or TOML, which have having to write an editor like git config a.b value. Maybe given option of open $(unicron -e) or simpler unicron -e open or ... code etc
• commandline will have to be revised for new commands
• any native bash commands like tail are best not handled with python otherwise its extra code and potential lost in functionality with streams and exit codes. If unicron is a bash script this is easier and maybe some commands go through unicron python script internally. Though the architecture is different for install bash than Python scripts.
• maybe a web server or python gui will help for running or viewing files but it takes away from the simplicity of unicron