batch command line tools

the clusterfunctions rely on issuing a couple of specific system commands. We do this by having (user configurable) R code where this cmds are generated and then executed.

Better approach might be this.
We shoud add another layer of abstraction. Which are the batch commands.
This is a small set of aliases / scripts.

Like this:
btsubmit
btkill
btlist

These we ship out, like we do with the cfs before, but the user could also adapt them if they have to.

This has a couple of advantages:

• it is easier for the user to locally adapt these simple bash scripts, then our current R code
• they are nicely seperately testable
• we kinda need a defined API here anyway
• if you put them in your path, you dont even need to remember whether you are on SLURM or TORQUE are whatever

I would actually ship out at some point some extra cmds which kinda only make sense on the console:
btkill-all: kill everything from the CLI the hard way
btlist: with an better overview option, so you can see what currently runs, with the state.

One even later add stuff like show-active-user or show-queues, which we now have as "bad throw-away" versions for lido and which do not work at other places.

Start by locating the current R code that generates and executes batch-system commands, then review how the existing cfs scripts are shipped. Done would require a defined set of configurable command aliases or scripts for submission, cancellation, and listing, with a clear API and coverage for the supported batch systems.