Tasks might interfere if another sequence was paused but task still running

[ermin-muratovic]

Environment

• Keptn Version (keptn version): 0.9.0

Describe the bug
If a sequence is paused, the currently running task might still take some time. If another sequence is triggered meanwhile, the sequence would start and it might happen that two tasks are executed at the same time.

As an example, in my case the helm-service failed installing/upgrading chart, because the deployment task in the paused sequence before was still running.

To Reproduce

Steps to reproduce the behavior:

1. Trigger a delivery sequence
2. Pause the sequence, while the deployment task is running
3. Trigger a new delivery sequence
4. See the new sequence starting and if both deployment task are running at the same time you can see the error

Expected behavior
I would expect the new sequence to wait for the task in the paused sequence to be finished.

Screenshots

[agrimmer]

This issue has the same root cause as #5557

[thisthat]

Duplicate of #5557