Add `Job` class with `uuid` field to support and simplify tracking, scheduling, executing, pausing, terminating, and monitoring of long running jobs on a local/remote machine

[sagikimhi]

[sagikimhi]

Launching a long running process can be achieved quite easily by utilising plumbum's NOHUP command execution modifier

Tracking statuses of long running jobs might require a little bit of work but it should still be relatively simple to achieve with a uuid field for each job that can be implemented by utilising pydantic's UUID types (maybe UUID4?) and later serialising the jobs to json or some binary format (e.g. parquet/sqlite-db) - then finished jobs can be found by searching for output files (stdout, stderr, retcode) in the application's dedicated output directory, still running jobs can be found by grepping the command args on the list of running processes and comparing the job start time for finding running jobs, and lastly if none of the above produced results the job can be considered pending