Migrate from CircleCI

We plan to move off the CircleCI system.

We can use GitHub actions for a lot of things.

If we need more than that, we can move onto the Apache Software Foundation's Jenkins instance. Our rationale for using that is that a couple of the current maintainers (@Poundex and @jonnybot0) have some background with Jenkins, which also has [a nice Groovy DSL for jobs](https://www.jenkins.io/doc/pipeline/steps/job-dsl/).

The [Apache Guide](https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=Jenkins) on Jenkins says we'll need access from the PMC. It looks like I can currently login to Jenkins and even create objects in the [Groovy section](https://ci-builds.apache.org/job/Groovy/).

Will look at replicating many of the build steps in Circle CI to GitHub actions first, as that's the least friction

Start by inventorying the existing CircleCI build steps and comparing them with GitHub Actions. Read the Apache Jenkins guide and inspect the Jenkins Groovy section; the migration is done when the current build steps are replicated in the selected CI system.

Written by the indexing model from the issue text.