feat: added ability to specify id for pc

[IlgamGabdullin]

Discussed issue here

Added new optional id?: string param in handleNewPeerConnection method and emited the id back in callback calculateNetworkScores, so now developers can use it that way

webRTCIssueDetector.handleNewPeerConnection(pc, 'some-id-1')
webRTCIssueDetector.handleNewPeerConnection(pc, 'some-id-2')
webRTCIssueDetector.handleNewPeerConnection(pc, 'some-id-3')

and in callback it wil be

onNetworkScoresUpdated: (scores) => scores.id; // some-id-X

@evgmel @desher @panov-va please take a look

[desher]

@IlgamGabdullin thank you for the PR.
I just want to suggest you to simplify the solution. Actually PeerConnection identifiers are not a part of this library so it is better to provide wrapped RTCPeerConnection object with inner id property. In total all you need to do here is add pc property to NetworkScores(onNetworkScoresUpdated callback payload).

[evgmel]

@desher Good idea 👍 @IlgamGabdullin , don't you mind making this changes in your PR?

[IlgamGabdullin]

@desher thank you for the idea!
I've pushed commits with your solution, seems to be working. Please take a look if I understood you correctly

[desher]

Awesome! Thank you @IlgamGabdullin
There's only one thing left for improvement. Please rename pc to connectionId to avoid possible confusion.

[vlprojects-bot]

🎉 This PR is included in version 1.10.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀