Create first release on Sonartype/Maven Central

[ascopes]

See instructions on https://issues.sonatype.org/browse/OSSRH-80456 and https://issues.sonatype.org/browse/OSSRH-80457

Congratulations! Welcome to the Central Repository!
io.github.ascopes has been prepared, now user(s) ascopes can:
Publish snapshot and release artifacts to s01.oss.sonatype.org
Have a look at this section of our official guide for deployment instructions:
https://central.sonatype.org/publish/publish-guide/#deployment

Depending on your build configuration, your first component(s) might be released automatically after a successful deployment.
If that happens, you will see a comment on this ticket confirming that your artifact has synced to Maven Central.
If you do not see this comment within an hour or two, you can follow the steps in this section of our guide:
https://central.sonatype.org/publish/release/

As part of our efforts to improve the security and quality posture of the open source supply chain,
we plan to enable additional scanning of dependencies for security alerts soon. Since you're already
hosting your source code in Github, you can get these insights today by enabling Sonatype Lift.
Sonatype Lift is free forever on public repositories! Lift tells you about open source
vulnerabilities
during code review, and goes beyond open source to scan your code for both code quality and security issues,
providing feedback right in your pull requests.
More information can be found at https://links.sonatype.com/products/lift/github-integration

Depends on #135, #136.

I will make a 0.0.1-M1 release first to verify the pipelines.

[ascopes]

https://github.com/ascopes/java-compiler-testing/releases/tag/v0.0.1-M1