Jobs to be treated as legacy unless there is a select statement

[hansrune]

We think the behaviour of what is regarded a legacy jobs should be changed. That is:

1. For submit hook: Unless there is a select in resource requirements, the job is held on submit. The submit arguments seem to be unavailable at this point
2. For periodic hook: Unless there is a select statement in the original submit arguments, the job is a legacy job

The need for this came up as we discovered that quote often, users simply use 'qsub -I -X -q queuename' to allocate a node for testing / interactive use of a GPU etc. In that case the job was not treated as a legacy job, and the needed placement and sharing from the queue defaults did not apply when they should. Result was that multiple users got allocated the same GPU nodes even if the queue defaults had scatter:excl as placement.

[hansrune]

@microsoft-github-policy-service agree