[OIL] Use mustache templates to build Java SDK + Add Java SDK build step to actions

[danilo-delbusso]

Unfortunately, I couldn't come up with an easy way to keep the same order of types in Types.java. The issue here is that they were added as they were found, so there was no specified order.

A good way to check would probably be to compare class structures instead. I'm happy to assist if possible.

The SDK sources are present in the PR's artifacts so you don't have to build them yourself.

This PR also adds the JAR to the release files.

Note that I did keep the existing side-effect operations of updating enums, types, etc.. I found that they weren't that much of an hassle to keep but feel free to weigh in.

For result of a release with the changes here see https://github.com/danilo-delbusso/xen-api/releases/tag/v60.1.3

[danilo-delbusso]

force push was a rebase on master to fix conflicts with #5610

I also added 36d9134 as part of the push

[kc284]

As above. It wil also need rebasing due to conflicts.

[danilo-delbusso]

force push is a rebase on master to fix merge conflicts

[xueqingz]

Here we use "UNRECOGNIZED" as default value for Jave SDK , can we use same default Enum value for Go #5981? @kc284

[kc284]

This is similar to the unknown_enum_value added in the Go PR. The result is that there are many enums (e.g. LatestSyncedUpdatesAppliedState or SriovConfigurationMode etc.) that have both unknown and unrecognized and I find this confusing from the client's perspective. I think the best way to handle it is like C# where we add unknown, but only for the enums that do no already have unknown.