fix Pydantic Field(ge/gt/le/lt=N) with int literal flagged as bad-argument-type on Decimal fields #3403

[asukaminato0721]

Summary

Fixes #3403

Pydantic range constraint metadata unwraps Annotated[...], handles Decimal | None, and accepts int/float-compatible constraint values for Decimal instead of relying only on strict subtype checks.

Test Plan

add test

[github-actions]

According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[rchen152]

This strikes me as likely not the right approach. It solves the problem for Decimal but not other types that may be runtime-coercible to one another, and it adds a new way of handling pydantic's runtime type coercion rather than reusing existing logic. But @migeed-z is the expert here.