Feature request: Improved handling of parametrized job names in the gui submitter

[rickrams]

Describe the problem

If you make a template with a parametrized job name i.e. name: '{{Param.JobName}}' when using the GUI submitter the first tab will prompt you to replace the parameter with a string that will then replace the parameter in the job template while the field to define the job name parameter is available on the parameters tab but harder to find.

Proposed Solution

Introduce special handling for fields on the first page of the GUI submission that are implemented as parameters instead of strings in the job template so the inputs are passed with the job as parameters and not edits to the template.

Example Use Cases

Key use cases are when working with the job template later - for portability to other queues or farms and re-submission - the template maintains their parameterized state so they can continue to be handled as parameters.