Possibly replace use of `styfle/cancel-workflow-action` with `cancel-in-progress`

[stevenengler]

We have a github CI workflow to cancel a previously run 'run-all-steps' workflow. We use the third-party styfle/cancel-workflow-action action with actions: write permissions for this. But since then github has added a cancel-in-progress workflow option. We should possibly switch to this instead if it serves the same purpose.

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs

tornettools/.github/workflows/cancel_prev_run_all_steps.yml

Lines 4 to 11 in df6ada5

	# Since the run_all_steps workflow is relatively expensive, only allow one
	# instance to run at once per branch, canceling obsolete runs.
	#
	# Based on https://github.com/styfle/cancel-workflow-action#advanced-pull-requests-from-forks
	#
	# TODO: should we replace this with 'cancel-in-progress'?
	# https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs
	name: Cancel previous run-all-steps

[sporksmith]

Nice - yeah I think this is what we want

For example, you can use the concurrency keyword immediately after where trigger conditions are defined to limit the concurrency of entire workflow runs for a specific branch:

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true