ASP-1915 Move SBATCH params to Job Script submission

[fschuch]

What

Currently in Jobbergate, the extra SBATCH params used for Job Script execution must be supplied when an Application is being rendered into a Job Script. The SBATCH params are injected into the Job Script code itself. Then, when the jobs are submitted to the cluster, those params are extracted from the script and re-written as API request parameters to the Slurm REST API.

Since the SBATCH params actually control job execution, they should instead be passed as part of the Job Submission process where a Job Script is submitted for execution. To this end, they should be changed to be a property of a Job Submission.

Why

• Make job_scripts more reusable so we should not need to create a new one from the template for every variation of params. This will result in fewer database entries and better scalability on the data backend
• Increase the function and usability of the API so that automation tools are easier to build and integration into other platforms is simpler
• Make things more maintainable and the existing implementation will be more flexible

Task: https://jira.scania.com/browse/ASP-1915

---

Peer Review

Please follow the upstream omnivector documentation concerning
peer-review guidelines.

[dusktreader]

Sorry for all the feedback here, but I think there are a few fundamental things to address.