* Update base image of Dockerfile
* Make github workflow "Docker tests" manually triggerable
* Don't possibly downgrade TLS version
* Update Dockerimage in ``run-in-docker.sh``
* Use Maven's non interactive mode inside workflow
* Don't spam log
* Use java 17
because it won't compile with 21
* Removed hard memory limit
as memory should be controlled by the container
* Update hub dockerfiles
* Updates docker images for CLI and Online to JDK 11 and Maven 3.6.3 builders
* Uses openjdk:11.0.8-jre-slim-buster rather than alpine as new image publishes CVEs
The defaults configured for GENERATOR_HOST didn't really make sense.
When running the docker container with `-P`, GENERATOR_HOST defaulted to
http://localhost. This caused download links for generated client/server
code to be incorrect. For most cases, there's no reason to provide
GENERATOR_HOST as the code already figures the appropriate
scheme/host/port from the originating request.
GENERATOR_HOST could still be used for more complex deployment
scenarios, for instance if a specific server is configured as a file
server. I haven't tested this scenario, and it may require mounting /tmp
as a volume when running within a container.
An update was made in #876 to remove version from the generated artifact
for openapi-generator-online. The change is missing the -online suffix.
My original glob pattern put the * in the wrong place for
maintainability.
