Change range/float range to value error and include member/obj in error message

[frmdstryr]

Currently a value out of range throws a type error even if it is the correct type.

This also includes the member name in the error message.

[frmdstryr]

Well it seems something changed in the float_range_handler with 3.12.

I started getting 'too small' validation errors with FloatRange(low=0, strict=False) for a value of 25. After updating the message to print the low value it was some huge value?

[frmdstryr]

If I change low value to a float low=0.0 it works it seems the low & high types are not checked.

[MatthieuDartiailh]

Can you rebase on main to fix the CI issue. Also it may be worth casting the low, high to preserve the fast validation path.

[frmdstryr]

The problem was there was no context validation for FloatRangePromote since the case was missing.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.67%. Comparing base (94baafc) to head (f57b23d).
Report is 15 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #221      +/-   ##
==========================================
+ Coverage   97.27%   97.67%   +0.39%     
==========================================
  Files          24       24              
  Lines        1065     1074       +9     
  Branches      158      162       +4     
==========================================
+ Hits         1036     1049      +13     
+ Misses         14       12       -2     
+ Partials       15       13       -2