feat: [draft] job types

[sammy-ette]

to facilitate #276 in my mind i am thinking that i should add a function for the hilbish job interface to just handle running generic commands outside of the shell intepreter. (this is a bit of an abstraction, and prevents me adding another command just to add a go native "command handle" management and whatever)

so to hold a less than part time spot in the job handler, jobs can have 2 types:

• intern
• part time

an "intern" job is just there to run commands for a runner. but if a runner wants to suspend it, the job will be promoted to part time and then sent the signal. using these terms might be a bit confusing, but itll still work anyway.

[sammy-ette]

hilbish.jobs.add will by default create a part time job. if a runner wants to add an intern job, like one that is implementing commands in any capacity, instead of using either hilbish.run or os.execute, or me adding another hack function to run a command and be able to create a job from it (as is done currently in the pr) to hilbish.jobs, they can add the 4th and new optional arg to specify the job type (intern or part time)