Automate regular Maven release deployment

[lauraharker]

We want to start regularly pushing Maven releases. I'll work with @jDramaix and @12wrigja on automating this process.

Possibly related issues: #4215 , #4168, #4208, #4161

[lauraharker]

The general plan is to:

• use the contents of https://github.com/google/closure-compiler/blob/master/.github/piper-cut-cl.json to automatically tag commits that correspond to a Google internal release commit
• regularly (at least once a month, maybe weekly) run a workflow to take the latest tagged commit & upload it to Maven

The goal of https://github.com/google/closure-compiler/blob/master/.github/piper-cut-cl.json is so that there's some signal that a given commit is good & safe to cut a release at, since we do a lot of internal testing already before releasing.

We also currently do internal releases at least 1x per week, sometimes 4x.

[thheller]

Any estimate on this? The last maven release is over a year old and I'd like to test some of the newer stuff?

[lauraharker]

I plan to try and push a Maven release this week manually, & then we'll work on more automation

[lauraharker]

I've pushed v20250402 to Sonatype: https://repo1.maven.org/maven2/com/google/javascript/closure-compiler/v20250402/. Should show up in https://mvnrepository.com/artifact/com.google.javascript/closure-compiler soon.

Since it's been more than a year, I wouldn't be surprised if something is broken. Please comment here if so.

[thheller]

Yes, a bunch of broken stuff. Mostly from me touching parts I'm probably not supposed to touch. For example JsAst being rolled into CompilerInput, when I have a bunch of reference to JsAst in my code. I'll see if actual stuff is broken once I get it to compile again.

[thheller]

Finalized the ugprade and everything is back in working order. All good from the CLJS front.