fix: validate parseInt result in getTokenFromUrl

[dajiaohuang]

Summary

修复 getTokenFromUrl 函数中 parseInt 可能返回 NaN 的问题。

问题

如果 chainId 不是有效的数字字符串（如 "abc"），parseInt(chainId) 会返回 NaN，但这个 NaN 会被直接返回而没有任何错误提示。

代码变更

// Before
chainId: parseInt(chainId),

// After
const parsedChainId = parseInt(chainId);

if (Number.isNaN(parsedChainId)) {
  throw new Error("Invalid token URL: chainId is not a valid number");
}

return {
  ...
  chainId: parsedChainId,
  ...
};

Fix

现在会验证 parseInt 的结果，如果返回 NaN 则抛出错误。

[vercel]

@dajiaohuang is attempting to deploy a commit to the Discove Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

Additional Suggestion:

Missing first-seen assignment in the valuesByType reduce causes all returned user data fields to be undefined

[vercel]

Default public hub api_key is applied unconditionally and (in three of four files) overwrites a caller's own api_key, breaking authentication against custom/private hubs.

[dajiaohuang]

Addressed the current review feedback in the latest commit. The user-data reducer now stores the first value for each type and replaces it only when a newer timestamp is seen, so first-seen fields are no longer lost. Validation: git diff --check passed. The local checkout has no Yarn binary/dependencies, so the package test suite could not run here.