Default toolchain to Java 22

[rodvar]

Follow up after merged PR -> #2965 (review)

• We use Java 17 but we would like to use Java 22 for the Bisq 2 app build/deployment. For publishing for mobile though we need java 17. It should be made default Java 22 and the publish task change it for the time it is running to Java 17. We should also rename the publishAll task to specify the special purpose for Bisq mobile (requiring Java 17).
• The Bisq verison in libs.versions.toml should be dynamically set from the root version
• Jitpack not used yet. Need to be figured out if we want to use it. For now we use MavenLocal

Important notes to develop a contribution for this issue

• ./gradlew publishAll needs to publish all jars to your maven local repo (~/.m2/repository) using Java 17
• assemble, build, install related task for release of bisq desktop should use Java 22 (see ./gradlew buildAll to understand which ones are involved)
• Ideally search in the code where the toolchain is set and default to 22 (instead of current 17) adding a mechanism to use J17 for jar publishing
• Finally, it would be great if we could publish J17 jars also to a public repo (like jitpack)