build: Add wasmer-java jar with all wasmer-jni dynamic libraries

[Zurcusa]

Description

Forcing the user to manually add the wasmer-jni libraries to their java extensions folder is quite a cumbersome task. Also not having all possible OS and architecture combinations in a wasmer-java.jar broke tests that are dependent on the wasmer library when running on different OS from the GH runners. That is fixes in this PR.

• What does this PR do? Abolish the manual process of importing the wasmer-jni library to the users java extensions.
• Why are these changes needed? For an improved user experience.
• How were these changes implemented and what do they affect? By using a wasmer-java jar that includes all wasmer-jni libs per os and arch.

Fixes #462

Checklist:

• [x] I have read the contributing guidelines.
• [x] My PR title matches the Conventional Commits spec.
• [x] My change requires a change to the documentation.
• [x] I have updated the documentation accordingly.
• [ ] I have added tests to cover my changes.
• [x] All new and existing tests passed.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud