adding slurm cmd option to CLI [3/n]

[luccabb]

Summary

allowing users to pass slurm cmd via the CLI and auto-ingest this in sbatch/srun output

Test Plan

observe how sbatch and srun now has the slurm cmd:

$ cscope job-gen task slurm --num-gpus=4 --partition=h100 --format=sbatch --time="1234234" --qos='learn' --slurm-cmd='python my.python.training'
#!/bin/bash
#SBATCH --cpus-per-task=96
#SBATCH --mem=999G
#SBATCH --ntasks-per-node=1
#SBATCH --gres=gpu:4
#SBATCH --partition=h100
#SBATCH --qos=learn
#SBATCH --time=1234234
python my.python.training
$ cscope job-gen task slurm --num-gpus=4 --partition=h100 --format=srun --tim
e="1234234" --qos='learn' --slurm-cmd='python my.python.training'
srun --cpus-per-task=96 --mem=999G --ntasks-per-node=1 --gres=gpu:4 --partition=h100 --qos=learn --time=1234234 python my.python.training

[gunchu]

How do we expect cscope job-gen task slurm... and such commands? My assumption was - they'll run it, copy paste the output where necessary (ex: top of their sbatch script) and keep iterating after that. The sbatch script can get quite large eventually.

[luccabb]

@gunchu yeah that's correct, this optional arg is just in case you want custom cmds to be appended to srun and sbatch

[gunchu]

Let's sit on this one for a while

[skalyan]

Can we convert this and PR99 to Draft state, given @gunchu guidance.