chore: upgrade to libp2p v2

[danisharora099]

This PR upgrades from libp2p 1.x to libp2p v2

Migration notes: https://github.com/libp2p/js-libp2p/blob/main/doc/migrations/v1.0.0-v2.0.0.md#the-libp2ppeer-id-factory-module-has-been-removed

[github-actions]

size-limit report 📦

Path	Size	Loading time (3g)	Running time (snapdragon)	Total time
Waku node	86.4 KB (+0.66% 🔺)	1.8 s (+0.66% 🔺)	14.8 s (+43.63% 🔺)	16.5 s
Waku Simple Light Node	136.94 KB (-0.5% 🔽)	2.8 s (-0.5% 🔽)	19.2 s (+59.69% 🔺)	21.9 s
ECIES encryption	22.88 KB (0%)	458 ms (0%)	6.2 s (+46.09% 🔺)	6.7 s
Symmetric encryption	22.37 KB (0%)	448 ms (0%)	2.6 s (-48.44% 🔽)	3 s
DNS discovery	70.6 KB (-3.15% 🔽)	1.5 s (-3.15% 🔽)	13.7 s (+54.83% 🔺)	15.1 s
Peer Exchange discovery	71.84 KB (-3.05% 🔽)	1.5 s (-3.05% 🔽)	12.1 s (+15.44% 🔺)	13.5 s
Local Peer Cache Discovery	65.17 KB (-4.22% 🔽)	1.4 s (-4.22% 🔽)	8.6 s (-22.57% 🔽)	9.9 s
Privacy preserving protocols	76.12 KB (+0.14% 🔺)	1.6 s (+0.14% 🔺)	8.8 s (-36.26% 🔽)	10.4 s
Waku Filter	80.95 KB (+0.8% 🔺)	1.7 s (+0.8% 🔺)	16.6 s (+61.42% 🔺)	18.2 s
Waku LightPush	75.68 KB (+0.87% 🔺)	1.6 s (+0.87% 🔺)	12.3 s (-12.97% 🔽)	13.8 s
History retrieval protocols	77.71 KB (+0.89% 🔺)	1.6 s (+0.89% 🔺)	9.6 s (-25.1% 🔽)	11.1 s
Deterministic Message Hashing	7.39 KB (0%)	148 ms (0%)	2.7 s (+19.15% 🔺)	2.8 s

[weboko]

Have no questions to the PR, we definitely need to upgrade libp2p.
But let's postpone till #2135 is merged.

It is risky to include into next release without proper dogfooding and we have some projects requiring #2137 and #2158

[danisharora099]

It is risky to include into next release without proper dogfooding and we have some projects requiring #2137 and #2158

Tests passing, PR is ready. There shouldn't be anything to dogfood with this internal upgrade, especially considering all tests now pass.

Merging it would also resolve #2174 @weboko

[weboko]

@danisharora099 did you try dogfooding it? I haven't but I'd like to have it done in various contexts before we merge

Contexts to check:

• how long and good light push functions
• is there any problems with outbound / inbound streams and connections
• are events propagating the same way we expect them: peer connect and disconnect, identify
• etc

Let's do this on Monday and if nothing caught - we can merge.

[weboko]

Suggested change

console.log(enr);