ci(java): build JNI release package

[eddyxu]

Provide a Github action workflow to release multi-platform JNI

[LuQQiu]

#2524
After add an extra step to set up nodejs 16 instead of default 20

      - name: Set up Node.js 16
        uses: actions/setup-node@v4
        with:
          node-version: '16'

the created jar can be used without the glibc issue
validated in linux x86 ubuntu 22 spark job

[rong-cai]

i felt like it should not be 3 jobs. but instead we should have 3 run matrix and at the very end we need to copy all 3 share lib (linux-x86, linux-arm, macos-arm) into the same fat jar?

this will still release 3 different JAR IIUC?

[eddyxu]

yes, if we call mvn deploy in three different job, we have to release 3 different jars (with different names?).
I am not sure that mvn will resolve dependency based on the system, like what pypi does.

[eddyxu]

we should have 3 run matrix and at the very end we need to copy all 3 share lib (linux-x86, linux-arm, macos-arm) into the same fat jar?

Put them into separate jobs, so that i can pass upload-artifcat/download-artifcat between the jobs. If we just run 3 parallel metrics, we need the 4th one to download the artifact?