2.0.12 — RAW and DATE inside a record

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

docker pull ghcr.io/srmadscience/mcpdbwizard:2.0.12

What is new in 2.0.12

A RAW or DATE field inside a record now tells a caller how it crosses.

Both were published as a bare {"type":"string"} — true, and useless. It does not say "send
base64", and it does not say the T is required, so the only way to learn either was to be
rejected. A scalar parameter of the same Oracle type has always said so, so this is the existing
contract reaching one level further in rather than a new one.

The RAW case was worse than a rejection, which is what makes it more than a schema nicety. Hex
is the spelling a person reaches for with RAW, and hex and base64 are both plain strings — so
sending hex was not refused. It decoded into different bytes and the procedure ran. The note
therefore says "base64, NOT hex" with an example, rather than just "base64".

Also in this release: each test class gets its own config directory, RUN_ON_START is documented,
and the undocumented MCPDBWIZARD_RUN_THIS_FILE escape hatch is withdrawn.