Multiple collections share sockets and peers when replicationWebrtc is used for synchronization

[croatialu]

This PR contains:

• A NEW FEATURE

Describe the problem you have without this PR

#5925

[croatialu]

You can experience the difference between before and after modification at this link

https://stackblitz.com/~/github.com/croatialu/rxdb-replication-webrtc

[croatialu]

Solution: Use closure to save data such as peers and sockets, and then each replicationWebrtc will try its best to reuse existing peers and sockets

How to use:

  const creator = getConnectionHandlerSimplePeer({})
  //                        ^ create a creator
  Object.keys(database.collections).map(async (key) => {
    return replicateWebRTC({
      collection:
        database.collections[key as keyof typeof database.collections],
      connectionHandlerCreator: creator,
      //                           ^ use the creator
      topic: dbName,
      pull: {},
      push: {},
    })
  })

[pubkey]

Hi @croatialu
Code changes look ok but this breaks the CI, please check.
Also we need at least one test to check the correctness of the new behavior.

[croatialu]

Hi @croatialu Code changes look ok but this breaks the CI, please check. Also we need at least one test to check the correctness of the new behavior.

Okay, I'll take care of it right away. Thanks for the reminder!