rdm: test invalid real-time clock values

[keeltrace]

AI-generated contribution. I am the human operator responsible for follow-up with maintainers. Please feel free to close this PR or request any changes.

Fixes #1510.

Adds SetRealTimeClockBadData, covering both straightforward out-of-range fields and the calendar edge cases suggested in the issue discussion:

• year below the minimum
• month 0 and 13
• day 0 and 32
• hour 24
• minute 60
• second 61
• February 30
• February 29 in a non-leap year

The test uses SendRawSet() with the REAL_TIME_CLOCK wire layout so values outside the PID store's declared ranges are actually sent to the responder instead of being rejected by local serialization. Each supported SET is expected to NACK with NR_DATA_OUT_OF_RANGE; an unsupported SET command class terminates the sequence normally.

Validation:

• python3 -m py_compile tools/rdm/TestDefinitions.py
• git diff --check

I also attempted TestRunnerTest.py, but this source checkout does not have the generated/installed ola.testing Python package available without a full OLA build, so that test cannot run directly from the shallow checkout.