Fix behavior of (uint)val in Mono to saturating behavior

[khushal1996]

This issue is created to track the discussion in the comment --> #97529 (comment)
PR #97529 changes the behavior of floating point to integer conversions on x86/x64. It allows the conversions to follow saturating behavior which .NET wants to standardize on.

Link to the failing build --> https://github.com/dotnet/runtime/pull/97529/checks?check_run_id=23012453843

@fanyang-mono for tracking this issue.

[tannergooding]

Just noting that this applies to all floating point -> integer conversions, they should all saturate under the new behavior we're standardizing against.