fix: connection robustness and flaky tests

[ganchoradkov]

Description

Reworked several parts of the client to address general stability issues and to increase robustness of the socket connections

• Implemented multi attempt connection logic in the relayer
• Implemented graceful handling of disconnects mid publish
• Reworked subscriber to attempt initial sub and let heartbeat retry to subscribe until success or reaching a timeout
• Reworked publisher to attempt initial publish and let heartbeat retry to publish until success or reaching a timeout
• Fixed several flaky tests that failed in bad network conditions with many disconnects
• Improved error logging

Type of change

• Chore (non-breaking change that addresses non-functional tasks, maintenance, or code quality improvements)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Draft PR (breaking/non-breaking change which needs more work for having a proper functionality [Mark this PR as ready to review only when completely ready])
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How has this been tested?

canary - 2.17.2-canary-rcnt-3
deployment - https://react-dapp-v2-git-chore-connection-test-reown-com.vercel.app/

Checklist

• I have performed a self-review of my own code
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

Additional Information (Optional)

Please include any additional information that may be useful for the reviewer.

[Cali93]

LGTM, left comments mainly around readability.

[Cali93]

Not directly related to this PR but createExpiringPromise could use Promise.race to be simplified and avoid potential race conditions.
This approach eliminates the need for manual clearTimeout calls because once the Promise settles, the other Promise in the race is ignored, and the timer will be garbage collected.

export function createExpiringPromise<T>(
  promise: Promise<T>,
  expiry: number,
  expireErrorMessage?: string,
): Promise<T> {
  const timeoutPromise = new Promise<T>((_, reject) =>
    setTimeout(() => reject(new Error(expireErrorMessage)), expiry),
  );

  return Promise.race([promise, timeoutPromise]);
}

[ganchoradkov]

will test it out duing tech debt week