Add slots support to abstraction

[ericfranz]

This is so we can remove custom code from https://github.com/OSC/ood-dashboard/blob/4b7b7f77caafb184de25fdb69250e1813342d6b9/lib/smart_attributes/attributes/bc_num_slots.rb#L55-L70 and we can remove use of the "native" args in batch connect apps like https://github.com/OSC/bc_osc_paraview/blob/20712bb87225c78c5ed6e2660a60805fb5a9093f/submit.yml.erb#L4-L7

┆Issue is synchronized with this Asana task by Unito

[ericfranz]

See https://slurm.schedmd.com/rosetta.pdf

These are relevant:

• node count
• cpu count
• generic resources
• cpus per tasks
• tasks per node
• memory size

We should itemize all of the resource requests we make at OSC across all of our apps. For example, can nodes 2:ppn=1:owens be split into separate flags like -l nodes=2 -l ppn=1 -l ??=owens? What would cover other use cases? How does DRMAA and DRMAA2 handle this with its slots interface? What about requesting gpu, etc.

[ericfranz]

Also we should produce a comprehensive list of examples from every external site that is willing offer up their examples. We would want a representative list of multiple sites for each adapter.

[ericfranz]

The goal here is we don't have to use "native attributes" for anything . An abstraction that would address this goal for us and every site on the advisory board and beyond would probably be appropriate.

[ericfranz]

Also see and document DRMAA 1 and 2's attempt at this problem. https://en.wikipedia.org/wiki/DRMAA