build(deps): bump network-connectors to 1.8

[MatiasOS]

Description

Bumps @openscan/network-connectors from 1.7 to 1.8. Release 1.8.0 ships ZcashClient (the Zebra RPC surface), and it fixes bip122: routing so Bitcoin and Zcash chain IDs no longer collide on their shared CAIP-2 prefix.

This is the first PR in the Zcash stack for #398; the following PRs build on it.

Related Issue

Closes #396

Type of Change

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

Changes Made

• package.json: @openscan/network-connectors goes from 1.7 to 1.8
• bun.lock: now resolves @openscan/network-connectors@1.8.0, with no other lockfile changes

Screenshots (if applicable)

N/A

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

Checked against the acceptance criteria in #396:

• ClientFactory.createClient still returns BitcoinClient for Bitcoin mainnet and testnet4, and returns ZcashClient for both Zcash chain IDs.
• rpcConfig.ts and useRpcLatencyTest.ts still typecheck against the widened rpcUrls type; npm run typecheck is clean.
• npm run build passes.
• The live Bitcoin e2e suite passes (24/24).
• npm run test:run passes (105 tests).

Biome still reports one warning, which already exists on dev: the unused getAlchemyBtcUrl in src/components/pages/settings/index.tsx.