Build the benchmark images from the master the chain tracks

[estebanzimanyi]

Dockerfile built MobilityDB from stable-1.3 while the jar it runs is
generated from the catalog of master, and it built without -DALL=ON, so the
library answered for a narrower family list than the surface the generator
emits. It now clones master and passes -DALL=ON, the flag CMakeLists.txt
turns into the family list.

Its JMEOS step cloned the branch fix-tests-using-docker into
/usr/local/jmeos, swapped a library into it and deleted its jars. Nothing in
the image ever read that directory — the branch was pinned for a checkout no
stage consumed. COPY jar/JMEOS.jar and the classpath entry beside it are the
systemPath model pom.xml itself has commented out: the shade plugin includes
*:*, and the 33 MB application jar carries functions/GeneratedFunctions.class.
Both go, and jar/ need not be assembled by hand before a build.

Dockerfile_q8_meos_kalman existed to build marianaGarcez/MobilityDB and patch
temporal_ext_kalman_filter into functions.java with two sed scripts.
That entry is declared in meos/include/meos.h on upstream master, so the
generator emits it and meos/examples/ais_ekf_clean.c is upstream as well. The
image differed from the base one in nothing else, and run_query.sh already
patches the entrypoint class it needed, so query 8 runs on the base image and
the file goes with its QUERY_DOCKERFILE entry. The two Query8_V2_Main
classes name the public MEOS entry rather than a fork.

mvn test is green over the module: 12 tests, 0 skipped.