2.0.10 — a metrics port a scrape can reach

Generates Oracle DAO, SOAP and MCP server code from a config file. This is the source drop for
2.0.10; the running article is the container image.

docker pull ghcr.io/srmadscience/mcpdbwizard:2.0.10

What is new in 2.0.10

A container could be entirely healthy and still refuse every Prometheus scrape.

The port was published, docker ps showed 0.0.0.0:9464->9464/tcp, the child had
MCP_METRICS_PORT in its environment — and nothing answered, with no line in any log saying why.
The exporter was listening on 127.0.0.1 inside the container, and Docker forwards a published
port to the container's bridge address, not its loopback.

The fix is in RuntimeManager rather than in the exporter's default, and the asymmetry is
deliberate: that default is right for the case it was written for, because the same class runs as a
plain library in somebody's own JVM on a real host, where switching metrics on must not be the act
that puts a server on a network.

Note this is the opposite of what the same code does for the MCP port, where loopback does not deny
access but channels it through the /mcp/{config} proxy — the only component that knows who is
calling.

The three metrics settings are also now documented where a Docker user will actually find them.