[Bug] Cancelled runs can still provision queued SUBMITTED jobs #4339

Summary

Stopping a run while one of its jobs is still SUBMITTED can leave the job in the provisioning queue. The run becomes TERMINATING, but the submitted-job fetch path can later provision an instance for that cancelled run. A related historical report is #3886; this report is not limited to capacity scarcity and points to a no-progress worker while offers are available.

Expected behavior

• Stopping a run terminalizes its SUBMITTED jobs that have never been provisioned.
• The submitted-job fetcher excludes jobs whose parent run is TERMINATING or terminal.
• A delayed queue followed by cancellation never creates an instance after cancellation.

Please verify the behavior on the current release and add regression coverage for both the stop transaction and submitted-job selection.