fix(rpcs): redact sensitive URLs and handle non-HTTP endpoints

[josealoha666]

Description

This PR addresses follow-up review items from #264 focused on the new RPC testing experience and E2E reliability.

Related Issue

Follow-up to: #264

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactoring
• Performance improvement
• Other (please describe):

Changes Made

• Redacted sensitive data in RPC URLs shown in UI:
  • Masks credential-like query parameters (e.g. api_key, token, secret, etc.)
  • Masks token-like path segments
  • Copy action now copies the redacted URL
• Fixed latency display semantics:
  • Offline/timeout/untested no longer show 0ms
  • They now show N/A
• Improved protocol handling in RPC tests:
  • Non-HTTP(S) endpoints (e.g. ws://, wss://) are marked as untested instead of being falsely marked offline
• Fixed RPC page copy consistency:
  • Updated EN/ES description text to match current behavior (re-test + copy flow)
• Fixed effect dependency stability on RPC page:
  • Removed dependency suppression and updated useEffect dependencies to avoid stale endpoint runs
• Split EVM E2E workflow into two parallel shards to reduce timeout risk:
  • shard-a: arbitrum/base/optimism
  • shard-b: bsc/polygon

Screenshots (if applicable)

N/A (logic/workflow focused changes).

Checklist

• I have run npm run format:fix and npm run lint:fix
• I have run npm run typecheck with no errors
• I have run tests with npm run test:run
• I have tested my changes locally
• I have updated documentation if needed
• My code follows the project's architecture patterns

Additional Notes

• Local validation executed:
  • npm run lint
  • npm run typecheck
• PR includes commits:
  • fix(rpcs): redact sensitive URLs and improve endpoint test handling
  • fix(rpcs): align copy text and stabilize auto-test effect deps
  • ci(e2e): split evm network tests into two parallel shards

[github-actions]

🚀 Preview: https://pr-267--openscan.netlify.app
📝 Commit: d09ba488e189efbf54d63a975dac9926fdca552f

[MatiasOS]

@josealoha666 This sounds better:

Compará el rendimiento de los endpoints RPC por red, volvé a probar proveedores y copiá las URLs para tu configuración.