Description
Is your feature request related to a problem? Please describe.
#1306 added GitHub Actions workflow definition files for running our test suite. That approach used separate workflow files for the "core" and "remote-data" tests because they are triggered differently. However, the two workflows have a lot in common, so it's a bit of a shame that the shared parts have to be repeated in the two files. For example when we inevitably want to add python 3.10 to the testing matrix, we'll have to edit two files instead of just one.
Describe the solution you'd like
As suggested by @wholmgren in #1306 (comment), it might be possible to partially combine the two workflow definitions into one by using GitHub Actions' "reusable workflow" feature: https://docs.github.com/en/actions/using-workflows/reusing-workflows
Describe alternatives you've considered
N/A
Additional context
N/A