feat(node): support connection string syntax for nodejs client creation

[T1B0]

Which issue does this PR address?

this PR add node sdk support for connection string syntax on client creation
accept common url like syntax new Client("iggy://iggy:iggy@127.0.0.1:8090");

note node:url module was not used since it would have introduced small differencez with rust and other sdk parsing, so connection string is manually parsed to match others sdk behaviors.

[codecov]

Codecov Report

❌ Patch coverage is 99.14040% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 84.06%. Comparing base (37d7eee) to head (a09ab2e).

Files with missing lines	Patch %	Lines
...oreign/node/src/client/client.connection-string.ts	99.15%	2 Missing ⚠️
foreign/node/src/stream/consumer-stream.ts	83.33%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #3917      +/-   ##
============================================
+ Coverage     84.03%   84.06%   +0.03%     
  Complexity     1358     1358              
============================================
  Files          1215     1217       +2     
  Lines        170820   170725      -95     
  Branches     138576   138239     -337     
============================================
- Hits         143547   143528      -19     
+ Misses        23411    23347      -64     
+ Partials       3862     3850      -12     

Components	Coverage Δ
Rust Core	84.93% <ø> (+<0.01%)	⬆️
Java SDK	66.67% <ø> (ø)
C# SDK	74.96% <ø> (ø)
Python SDK	90.10% <ø> (ø)
PHP SDK	85.65% <ø> (ø)
Node SDK	95.97% <99.14%> (+0.16%)	⬆️
Go SDK	68.29% <ø> (ø)

Files with missing lines	Coverage Δ
foreign/node/src/client/client.config.ts	100.00% <100.00%> (ø)
foreign/node/src/client/client.connection.ts	96.19% <100.00%> (-0.27%)	⬇️
foreign/node/src/client/client.socket.ts	95.69% <100.00%> (+0.01%)	⬆️
foreign/node/src/client/client.ts	97.17% <100.00%> (-0.02%)	⬇️
foreign/node/src/constant.ts	100.00% <100.00%> (ø)
foreign/node/src/stream/consumer-stream.ts	76.22% <83.33%> (+0.16%)	⬆️
...oreign/node/src/client/client.connection-string.ts	99.15% <99.15%> (ø)

... and 46 files 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.

[hubcio]

a few notes from comparing against the rust parser. one i'd want fixed before merge - the credential echo in errors.

these landed outside the diff:

foreign/node/src/stream/consumer-stream.ts:81 and :113 - singleConsumerStream and groupConsumerStream still take ClientConfig, so passing a connection string fails to compile (TS2345). they call the widened getClient, and since getClient isn't exported they're the only place users can reach the widening.

foreign/node/src/client/client.connection.ts:86-90 - reconnect timer is never unref'd and the handle isn't kept, so unlimited means the process can't exit and destroy() can't cancel a wait already in flight. the heartbeat timer next door unrefs itself with a comment saying why. pre-existing, but this PR makes unlimited a one-word option and ships it in the new e2e.

foreign/node/src/client/client.config.ts:61 - error says heartbeatInterval in raw ms at someone who typed heartbeat_interval=1000h.

nothing tests the tls branch - the pre-merge action runs tls.system.e2e.ts, which builds from an object config, so the parser never gets hit.