Warnings when disabling Docker extension

[ebaron]

Our downstream builds do not use the Docker extension. The following keys in the application.properties end up generating warnings upon startup:

cryostat-reports/src/main/resources/application.properties

Lines 1 to 5 in 2199e85

	quarkus.container-image.build=true
	quarkus.container-image.registry=quay.io
	quarkus.container-image.group=cryostat
	quarkus.container-image.additional-tags=latest
	quarkus.docker.executable-name=podman

2022-11-22 19:54:53,265 WARN  [io.qua.config] (main) Unrecognized configuration key "quarkus.container-image.build" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2022-11-22 19:54:53,265 WARN  [io.qua.config] (main) Unrecognized configuration key "quarkus.container-image.group" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2022-11-22 19:54:53,265 WARN  [io.qua.config] (main) Unrecognized configuration key "quarkus.container-image.additional-tags" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2022-11-22 19:54:53,265 WARN  [io.qua.config] (main) Unrecognized configuration key "quarkus.docker.executable-name" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
2022-11-22 19:54:53,265 WARN  [io.qua.config] (main) Unrecognized configuration key "quarkus.container-image.registry" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo

This doesn't impact the application running, but it would be nice to move these properties and the container build to a Maven profile. It can be active by default to not cause any development workflow changes.