Not tested, not finished, just a draft.

… for backwards compatibility.

This should keep the existing cache valid and re-usable.
Otherwise, we would create a new cache structure within the existing cache, with redundant entries.
With this change, we limit the redundancy to arch- or classifier-specific entries.

We could include x64 and ARM64 dependencies for Z3.
However, the default stays by only x64.

…rs, but only all other files.

This cleanup aligns better with Maven guidelines.
This is a small change for all upcoming publications to Maven and the Maven users.

…cture.

Additionally, we upload Java sources and JavaDoc for z3 to the Maven repository.

We need to test whether the uploaded files work as expected.

Let the user decide what to load,
e.g. on a minimal system only load for one specific OS and arch.

See Z3Prover/z3#7419 for details.
If required, the Z3 parser automatically converts Boolean formulas `f` to e.g. `ITE(f 1 0)`,
which makes them comparable to Integer symbols and numbers 0/1.

…tacktrace.

…tacktrace.

…3 v4.13.2 and incompatible msvcp140.dll.

See Z3Prover/z3#7420 for details.
This update is just a test. If it does not work, we will revert it.

…s with Z3 v4.13.2 and incompatible msvcp140.dll."

This reverts commit 07a4015.

… for multiple architectures.

We aim for backwards-compatibility and provide the x64-version as default for most public configurations.
The solver-specific configuration "runtime-z3" does provide more than x64, and comes with arm64 included.

…ate dependencies.

- prepare for distinct architectures x64 and arm64 under Linux.

- remove MPIR usage and replace it with GMP headers.
  MPIR is unmaintained since several years.

- update GMP to v6.3.0 and JDK to v17

This reverts commit 07a4015.

…ure-solver-binaries-z3

…Instead, we use a plain Java-based solver as reference.

….04 and 20.04, using only GLIBC_2.27.

…ure-solver-binaries-z3

…inux

This does not change the output of the script.