ci(bindings/java): enable auto staging JARs on Apache Nexus repository

[tisonkun]

No description provided.

[tisonkun]

Waiting for approval - https://issues.apache.org/jira/browse/INFRA-24928

We need this action to set up protoc on all platforms instead of manually tweaks.

[tisonkun]

@Xuanwo we can proeprly staging the artifacts now!

But I noticed that the staged osx_aarch64 JAR contains x86_64's dylib. I'm digging into the details and will remove the debugging trick before calling a merge.

[tisonkun]

@Xuanwo @suyanhanx This is ready for review now!

[tisonkun]

I have a few thoughts on these triggers:

1. I keep the workflow_dispatch so that we can somehow debug the workflow. It's possible that we retain only this trigger and let the RM trigger release staging on a tag manually. But let's try to do it fully automatically now.
2. For the tag triggers:

I create a pattern that only staging for each RC. This is because we only staging the artifacts instead of fire the release. The staging artifacts can be found at https://repository.apache.org/#stagingRepositories. For example, the last commit debugging commit staging orgapacheopendal-1012:

I'll click "Drop" to clean up. And a RM should "Drop" on vote failed; "Close" and later "Release" on vote passed.

Note that since we tag -rcN Git tags now, other bindings releases should filter out the trigger on RCs, or following the process here to staging on RCs.

[Xuanwo]

Thanks a lot! Let's go!