Giving a Date._parseable but invalid DateTime-ish String value into a TimeZone aware AR column immediately raises since 4.0.x.
This regression was caused by 41ff6a1 which stopped rescuing errors when parsing.
This patch brings back the AR3 behaviour that sets nil in such case instead of raising.
Fix AR 4 regression that setting a broken Time-ish String raises Argu…
I guess this is a dup of #11867
@amatsuda looks like this bug is being addressed in #11867. Any reason to keep it open or can we close the issue?