chore: remove styfle/cancel-workflow-action usage

[MichaelDeBoey]

• https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#concurrency

• https://github.blog/changelog/2021-04-19-github-actions-limit-workflow-run-or-job-concurrency

• The fully-formed ref of the branch or tag that triggered the workflow run. For workflows triggered by push, this is the branch or tag ref that was pushed. For workflows triggered by pull_request, this is the pull request merge branch. For workflows triggered by release, this is the release tag created. For other triggers, this is the branch or tag ref that triggered the workflow run. This is only set if a branch or tag is available for the event type. The ref given is fully-formed, meaning that for branches the format is refs/heads/<branch_name>, for pull requests it is refs/pull/<pr_number>/merge, and for tags it is refs/tags/<tag_name>. For example, refs/heads/feature-branch-1.

  https://docs.github.com/en/actions/learn-github-actions/contexts#github-context

[codecov-commenter]

Codecov Report

Patch and project coverage have no change.

Comparison is base (6fcf8e3) 100.00% compared to head (2b621e2) 100.00%.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #439   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           25        25           
  Lines          649       649           
  Branches       250       250           
=========================================
  Hits           649       649           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.