GeezerVison

Fixes #418.

When a server returns a UDP response larger than the advertised payload size without setting TC, the receive buffer cuts it off and parsing fails before the resolver can retry over TCP. Read one additional byte, bounded by the DNS message limit, to distinguish an oversized response from a valid response that exactly fills the buffer. Parse an oversized response as truncated, then retain the existing ID, question, opcode and TSIG checks before using the TCP fallback. ignoreTruncation=true retains its existing receive and parsing behavior.

Validation on macOS arm64 / OpenJDK 21.0.12.1:

• The two oversized regression cases fail on the original production code; all eight regression cases pass with the fix, including exact-capacity, ordinary malformed, wrong-ID, TC and ignore-truncation controls.
• mvn -B -ntp -Dgpg.skip -DexcludedGroups=concurrency verify: 1789 tests, 0 failures/errors, 28 skipped; compatibility, Spotless and Checkstyle checks pass. The concurrency exclusion and signing skip match the project's JDK 21 CI settings. The existing baseline suite reports 1781 tests with the same 28 skips.
• A local UDP/TCP stub returning 2741 bytes without TC now returns all 24 TXT records through TCP; the original code raises WireParseException without attempting TCP. The small UDP and forced-TCP controls remain successful, and ignore-truncation does not retry.

AI assistance: OpenAI Codex helped investigate, implement and validate this change.