fix: Set cancel-in-progress to false in infra_apply

[christian-calabrese]

List of changes

Motivation and context

Type of changes

• [ ] Add new resources
• [ ] Update configuration to existing resources
• [ ] Remove existing resources

Does this introduce a change to production resources with possible user impact?

• [ ] Yes, users may be impacted applying this change
• [ ] No

Other information

[gunzip]

can we enqueue further runs instead of running them in parallel?

[christian-calabrese]

can we enqueue further runs instead of running them in parallel?

I think that's already the behavior due to the concurrency group. However, as the doc states, only one job can be enqueued

When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be pending. Any pending job or workflow in the concurrency group will be canceled. This means that there can be at most one running and one pending job in a concurrency group at any time.