For some reason, I need to pin the Java install when using act. This is not
needed when using the GitHub Actions runner, so add an escape clause to
only run this extra step when using act.
We have two CI workflows with the name "test" (three if you count
"test-14"). This ambiguates the job name, and results in act running both
unit tests and integration tests when running `act -j test`. Fix that by
changing the names.
The publishing action assumes that main in package.json points to the
entrypoint of the action. Since v1.2.0, however, that is no longer the
case. Rather than try a new system (or dive deep into the internals of
npm and what every directive means), we'll trick the action into uploading
the correct script by modifying the package.json file right before upload.
Add that hack.