[pickers] Add verification to disable skipped hours in spring forward DST

[arthurbalduini]

(expects to) close #12403

This is an approach to prevent current inconsistency when selecting a value that is skipped on spring forward DST event.

Although it's debatable, perhaps hidding the value could make sense, but this wouldn't be a good UX for TimeClock. I'm verifying when the adapter doesn't return the same hour as the one of the option.

Before

Screen.Recording.2024-10-25.at.14.47.45.mov

After

Screen.Recording.2024-10-25.at.14.49.10.mov

Missing

• Issue with TimeClock not rendering disabled hour in first render

Screen.Recording.2024-10-25.at.14.51.34.mov

• Tests

[mui-bot]

Deploy preview: https://deploy-preview-15115--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against 5b5544a

[LukasTy]

Great idea, this looks like an interesting compromise. 👍
I fear this could raise questions to end users and developers alike if a specific hour is disabled without any explanation. 🙈
However, I'm not against trying this out without any extra tooltips or something similar as it would bring these components closer to the DigitalClock in behavior parity. 🤔
WDYT about the proposal @flaviendelangle?

[flaviendelangle]

If I understand correctly, this disabled hour only occur in spring when entering DST.
If so, I'm fine with the solution, if it can prevent some weird scenario it seems like a nice compromise