build: consume jclara and xmsg from code.jlab.org

[c-dilks]

xmsg changes

bumping JAR from 2.3 to our deployed version on code.jlab.org, which we have tagged as 2.5

From what I can tell, most of these changes are to gradle files and testing. The commits that stand out to me as being substantive source code changes are:

• JeffersonLab/xmsg-java@d6a2ff5
• JeffersonLab/xmsg-java@46478a4
• JeffersonLab/xmsg-java@3463809

Here are the full diffs:

• from v2.3 -> v2.5: https://code.jlab.org/hallb/clas12/coatjava/xmsg-java/-/compare/v2.3...v2.5?from_project_id=959
• from v2.3 -> master before we forked to code.jlab.org: JeffersonLab/xmsg-java@v2.3...3463809
• difference between decompiled JARs: https://code.jlab.org/dilks/jarchaeology-xmsg/-/merge_requests/1/diffs

jclara changes

This is the CLARA we depend on at build time; we use a different version with run-clara.

It looks like we forked at commit 4b414bc7; I added the tag v4.3 to our fork at the same position as the upstream's v4.3, since it was missing, and I assume that this is the version the clasweb 4.3 JAR was deployed from.

Looking at the diff via the following command, I don't see any changes that will impact us, at least at first glance:

git diff v4.3..6.2 **/*.java

Here are the full difs:

• from v4.3 -> 6.2: https://code.jlab.org/hallb/clas12/coatjava/clara-java/-/compare/v4.3...6.2?from_project_id=243 (better to clone the repo and view locally...)
• difference between decompiled JARs: https://code.jlab.org/dilks/jarchaeology-jclara/-/merge_requests/1/diffs

additional changes

• remove gson convergence conflict resolution; alert explicitly needs it at runtime though, so add it along with djl in its copy-dependencies execution, which ensures the correct gson version is used