[JVM] Publish `next` artifacts to release repository to make them easier to consume

[Jeremiah Zucker]

Is your feature request related to a problem? Please describe.

For consumer that would like to consume bleeding edge changes, they currently need to pull any canary (PRs) or next (prereleases from main) from the snapshot repos. Configuring this repo can have a negative impact on consumer build performance.

Describe the solution you'd like

We should continue pushing canary builds to the snapshot repos, as those are strictly for testing and may not be complete, or correct, code. However, next builds have explicitly been reviewed and merged into our main branch. We can have confidence in the stability of those artifacts as prereleases and can publish them to release repositories (similar to how alpha and beta artifacts are published for other projects).

Additional context

https://maven.google.com/web/index.html#android.arch.core:common