Verify the SQLite JDBC jar's SHA-256 in the Lucee test images #4595

The Lucee 5, 6 and 7 test images (tools/docker/lucee{5,6,7}/Dockerfile) download sqlite-jdbc-3.50.3.0.jar with wget. wget exits non-zero on HTTP errors, so a failed request already fails the build. But the jar is never checked against a known hash. A damaged or substituted jar would be baked into the image and only surface at test time, as Tomcat's zip END header not found or org.sqlite.JDBC not found.

The CI workflows now fetch the driver through tools/ci/fetch-sqlite-jdbc.sh, which checks Maven Central's published SHA-256 (#4594). The Dockerfiles could do the same in their RUN steps:

 && echo "a3f53a2aa15ae9425a9e793bbe9c8e5288febeb4b65ef5c1a4e80d4c2045cf08  /path/to/sqlite-jdbc.jar" | sha256sum -c -

The same applies to the other artifacts those images fetch: the Lucee H2 and Oracle extensions and the Oracle JDBC driver.