Ensure that integer parsing correctly handles non-zero fractional data

[tannergooding]

This resolves #94971

[tannergooding]

CC. @stephentoub.

This is fixing a regression introduced in .NET 8, so we likely want to backport into .NET 8 and .NET 9 RC2

[tannergooding]

Just noting for reviewers that this Parse_Invalid_TestData is reused by the other integer types as part of their parsing validation logic.

For example:

runtime/src/libraries/System.Runtime/tests/System.Runtime.Tests/System/SByteTests.cs

Lines 266 to 269 in b4d4333

	foreach (object[] widerTests in Int32Tests.Parse_Invalid_TestData())
	{
	yield return widerTests;
	}

and

runtime/src/libraries/System.Runtime/tests/System.Runtime.Tests/System/Int64Tests.cs

Lines 303 to 313 in b4d4333

	foreach (object[] objs in Int32Tests.Parse_Invalid_TestData())
	{
	if ((Type)objs[3] == typeof(OverflowException) &&
	(((NumberStyles)objs[1] & NumberStyles.AllowBinarySpecifier) != 0 || // TODO https://github.com/dotnet/runtime/issues/83619: Remove once BigInteger supports binary parsing
	!BigInteger.TryParse((string)objs[0], (NumberStyles)objs[1], null, out BigInteger bi) ||
	(bi >= long.MinValue && bi <= long.MaxValue)))
	{
	continue;
	}
	yield return objs;
	}

[tannergooding]

/backport to release/9.0

[github-actions]

Started backporting to release/9.0: https://github.com/dotnet/runtime/actions/runs/10474544009

[tannergooding]

/backport to release/8.0-staging

[github-actions]

Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/10474548878