fix(v3-client): Guard trace summary timestamp params against out-of-range Date

[okxint]

Problem

fetchTraceSummaries guards startUs/endUs with Number.isFinite, but Number.isFinite(1e20) is true. Values that large (beyond Date's maximum of 8.64×10¹⁵ ms) cause new Date(startUs / 1000).toISOString() to throw RangeError: Invalid time value, crashing the function before fetch() is ever called.

Fix

Introduce an intermediate Date object and guard with Number.isFinite(date.getTime()) before serialising. new Date() with an out-of-range argument produces an Invalid Date whose getTime() returns NaN, so Number.isFinite(NaN) === false silently drops the parameter — matching the existing comment "drop malformed URL params gracefully" and consistent with how the Number.isFinite(startUs) check above it works for non-finite inputs.

-    if (Number.isFinite(startUs) && startUs > 0)
-      params.set('query.startTimeMin', new Date(startUs / 1000).toISOString());
-    if (Number.isFinite(endUs) && endUs > 0)
-      params.set('query.startTimeMax', new Date(endUs / 1000).toISOString());
+    const startDate = Number.isFinite(startUs) && startUs > 0 ? new Date(startUs / 1000) : null;
+    if (startDate && Number.isFinite(startDate.getTime()))
+      params.set('query.startTimeMin', startDate.toISOString());
+    const endDate = Number.isFinite(endUs) && endUs > 0 ? new Date(endUs / 1000) : null;
+    if (endDate && Number.isFinite(endDate.getTime()))
+      params.set('query.startTimeMax', endDate.toISOString());

Fixes #4284

[github-actions]

Hi @okxint, thanks for your contribution! To ensure quality reviews, we limit how many concurrent PRs new contributors can open:

• Open: 4
• Limit: 1

This PR is currently on hold. We will automatically move this into the review queue once your existing PRs are merged or closed.

Please see our Contributing Guidelines for details on our tiered quota policy.