Add JavaDoc and sources for JavaSMT and all solvers

[daniel-raffler]

Hello,

this PR will add missing JavaDoc and sources jars for JavaSMT and its solvers:

• JavaSMT
• JavaSMT (Yices)
• cvc4 (see Rerelease CVC4 to add JavaDocs and sources #640)
• cvc5
• Princess (JavaDoc only)
• SmtInterpol (JavaDoc only)
• yices
• z3 legacy

For JavaSMT itself the JavaDoc jar gets built, but just isn't published by Ivy. For most of the solvers we'll first have to generate the JavaDoc files

[daniel-raffler]

@kfriedberger Should I also update the solvers that are still missing (cvc4, simtinterpol, z3 legacy)? We don't have JavaDoc/sources for them, but then again they may never get updated

[kfriedberger]

Some minimal JavaDoc-Jar would be nice to have for all our publications, however, for solvers, priority is quite low.
Higher priority is at JavaSMT itself and the JavaSMT-Yices bindings (without Yices itself).

[daniel-raffler]

All solvers (except cvc4) should be working now. We'll have to recompile the binaries for cvc5, z3legacy and yices, but this can be done next time we update those solvers. Once we have the new binaries, we should remember to also update the dependency in ivy.xml to include the sources and JavaDoc files:

[daniel-raffler]

@kfriedberger

While working on #637, I came across the issue, that Maven requires JavaDow for each release. That can be fixed/patched when releasing into Maven. However, I would like to see JavaDoc being also part of the Ivy-based publication process.

This PR should at least add JavaDoc for java-smt and javasmt-yices2. For the solver modules it's a little more complicated: If the module has a *.jar in it (f.ex javasmt-solver-cvc5) we now include JavaDocs and a sources *.jar along with it. However, these are the docs/sources for the (native) solver bindings, which may not be entirely what we want. Furthermore, some solver (f.ex mathsat) don't have a *.jar file as we included the JNI bindings directly in our code. In that case, there is just nothing that could be documented by JavaDoc...

I think one solution might be to further split up the modules and move all solvers out of java-smt and into their own module, similar to how it was already done for yices. That way, the JavaDoc for the modules would at least contain a single class (*SolverContext), and the sources jar would package the sourcecode of the solver backend in JavaSMT

Can you also take a look at other projects of Sosy-Labs well, e.g., https://github.com/sosy-lab/java-common-lib . It looks like all Java-based software artifacts of Sosy-Lab share the same code Ant/for Ivy here, and we forgot to provide proper JavaDoc-Jars.

For common the fix is essentially the same as 5f79946. Unfortunately the ivy.xml file is not part our project template, so we'll have to fix this in each project separately

[kfriedberger]

cvc5 was updated to latest version. lgtm.

[kfriedberger]

• some minor parts fixed in latest commits. ✅
• sovlers are published in corresponding version, including JavaDoc. ✅

can be merged.