Do not allow concurrent github action run to prevent multiple actions modifying the artifact at the same time

[binamkayastha]

https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency#example-using-concurrency-and-the-default-behavior

[zlowen]

There are two options for functionality:

single (default): At most one job or workflow run can be pending in the concurrency group. When a new job or workflow run is queued, any existing pending job or workflow run in the same group is canceled and replaced.

max: Up to 100 jobs or workflow runs can be pending in the concurrency group. When the queue is full, any additional jobs or workflow runs are canceled.

To me it makes sense to use single. That way if a dev is makes multiple commits in quick succession the workflow will only use the most recent. I don't think we would need the intermediate builds. Open to hear others' thoughts on this