fix(validation): correct int-width bound in GetIntFromInterface

[Phil-Browne]

Extracted from #535 (ESD-1648) as a standalone fix, orthogonal to the prompt/validator-parity work in that PR.

GetIntFromInterface compared a JSON-derived float64 against math.MaxInt directly. float64(math.MaxInt) rounds up to 2^63 only when int is 64 bits, so on platforms where MaxInt fits exactly in a float64 (e.g. 32-bit int, js/wasm) the check wrongly rejected the true max int.

• Use >= float64(math.MaxInt)+1 as the exclusive upper bound, correct on either int width.
• Derive the boundary tests from math.MaxInt instead of a hardcoded 2^63 so they stay in range on any platform.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.58%. Comparing base (9ba6a3b) to head (7bbcb18).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #538      +/-   ##
==========================================
+ Coverage   78.57%   78.58%   +0.01%     
==========================================
  Files         192      192              
  Lines       18522    18522              
==========================================
+ Hits        14553    14555       +2     
+ Misses       2904     2902       -2     
  Partials     1065     1065              

Files with missing lines	Coverage Δ
internal/validation/conversion.go	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

Fixes a platform-dependent overflow check in internal/validation.GetIntFromInterface when converting JSON-derived float64 values to int, ensuring correct behavior across 32-bit (including js/wasm) and 64-bit int targets.

Changes:

• Adjusts the float64→int upper-bound validation to use an exclusive bound (v >= float64(math.MaxInt)+1) to avoid float64(math.MaxInt) rounding pitfalls.
• Updates unit tests to use math.MaxInt-derived boundary values (instead of hardcoded 2^63) for platform portability.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
internal/validation/conversion.go	Updates float64 range validation logic to correctly reject out-of-range values regardless of int width / float64 rounding behavior.
internal/validation/conversion_test.go	Extends test coverage around the upper-bound behavior using math.MaxInt-derived values.

[penzeliz-megaport]

Reviewed for correctness; no findings. LGTM.