[release/9.0] Harden parsing of [Range] attribute values

[github-actions]

Backport of #59043 to release/9.0

/cc @captainsafia

Description

This change hardens the parsing logic for [Range] attributes to handle:

• Values that cannot be mapped to a decimal as is required by the minimum and maximum keywords in the OpenAPI schema, like DateTime.
• Handling for InvariantCulture as is set in RangeAttribute.ParseLimitsInInvariantCulture.

For scenarios where the range value is too large to be represented as a decimal, this implementation will no-op and not set the corresponding minimum or maximum in the OpenAPI document.

Fixes #57390

Customer Impact

Prevents unhandled exceptions when customers use the Range(object, object) overloads of the Range attribute instead of those that take a double/integer. There's no immediate workarounds for this bug outside of removing the attribute.

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Change localized to Range attribute handling in OpenAPI package.

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

[captainsafia]

Good bot! 🤖

[captainsafia]

Approved via email.