(Re)scheduled batch periodic scenario reported as not running

[jedrz]

To reproduce the issue:

• Scheduled scenario is deployed by the batch periodic engine, but the job fails during execution and is reported as FAILED on Flink afterwards.
• NK correctly reports it as not running.
• User decides to cancel and deploy scenario. Scenario should be scheduled but NK still reports the scenario as not running because the old, failed job is still visible on Flink console.