Add Aerie Maven artifacts to Maven Central

[camargo]

See: https://maven.apache.org/repository/guide-central-repository-upload.html

This would help decrease the barrier to entry a bit since right now you need a GitHub account to use the Aerie Maven GitHub packages.

[skovati]

Unfortunately, publishing to Maven Central is quite a can of worms. Maven Central simply acts as a centralized reverse proxy, and packages synced to Maven Central must actually be hosted on some third-party repo like Sonatype's OSSRH. This requires requesting an account through their Jira, creating and publishing a PGP key, signing binaries, and then manually syncing them to Maven Central.

Since the goal of this ticket is to just have publicly accessible maven packages, I looked into making our Github maven packages public. Unfortunately, this isn't supported first class by Github, (see this long-running discussion for details), but a workaround exists where you simply create a PAT that has read-only access to an organizations packages, and publish this publicly for those who want to consume your packages. Since public packages are 100% free according to Github's pricing page, this is a decent option while we wait for Github to natively support downloading public packages sans auth.