Possibility to provide user-defined ERF file for JSRUN_ERF LM

[mtitov]

User has an extended version of the ERF file (compare to a basic one generated by RP LM JSRUN_ERF)

• Could this information be provided within td.metadata? e.g., {'lm': {'erf': '<file_path>'}} and user is responsible to set input_staging if file_path is not an absolute path.

Example for the user defined ERF

app 0: <user_defined_application>  # probably this could be skipped
cpu_index_using: logical
overlapping_rs: allow
oversubscribe_cpu: warn
oversubscribe_gpu: allow
oversubscribe_mem: allow
launch_distribution: packed
rank: <rank_id>: { host: <host_id>; cpu: {<cpu_range>} ; gpu: {<gpu_id/gpu_range>} ; mem: {<mem_range>} } : app 0
rank: ...

---

p.s., this task is part of the UQ and Workflow Management Software working group, and specifically for the Lattice QCD community

---

p.p.s., additionally, review available metadata keys: as part of this effort - make an "inventory" of other keys used within metadata attribute.