Fix exception on parse failure for unsigned types in BindConverter

[irfanajaffer]

Description:

When attempting to convert negative values to unsigned integer types (uint, ushort, ulong, byte), the TypeConverter throws an ArgumentException. While the BindConverter correctly catches this exception and returns false (as expected behavior), the test suite lacked comprehensive coverage to verify this behavior across all unsigned types and edge cases

Root Cause

The BindConverter uses TypeDescriptor/TypeConverter for unsigned integer types (uint, ushort, ulong, byte, sbyte) since they don't have explicit handling in the ParserDelegateCache. When invalid values (like negative numbers for unsigned types) are passed, the TypeConverter throws ArgumentException, which is properly caught and handled by returning false.

Testing

Added comprehensive unit tests in BindConverterTest.cs to validate handling of unsigned integer types across all key scenarios. The tests ensure:

✅ Valid conversions succeed as expected
✅ Negative inputs return false without throwing (verifies ArgumentException handling)
✅ Out-of-range values return false (verifies OverflowException handling)
✅ Null and empty string inputs are handled gracefully
✅ Nullable unsigned type conversions behave correctly
✅ Boundary values (MinValue/MaxValue) are processed accurately

Fixes #42435