chore(store)!: move protocol implementation opinions to `@waku/sdk`

[danisharora099]

Problem

1886

Solution

Moves away the abstraction of using multiple peers, along with the offered APIs to make queries for store by:

• creating a new class StoreSDK (and renaming protocol implementation to StoreCore
  • StoreCore contains one API that returns an AsyncGenerator: *queryPerPage
  • StoreSDK offers different APIs to query, that uses queryPerPage
  • Increases readability and modularity

Notes

• https://github.com/waku-org/js-waku/issues/1886

Contribution checklist:

• [ ] covered by unit tests;
• [ ] covered by e2e test;
• [x] add ! in title if breaks public API;

[github-actions[bot]]

size-limit report 📦

Path	Size	Loading time (3g)	Running time (snapdragon)	Total time
Waku node	185.75 KB (+0.26% 🔺)	3.8 s (+0.26% 🔺)	3.1 s (+84.81% 🔺)	6.8 s
Waku Simple Light Node	185.45 KB (-0.03% 🔽)	3.8 s (-0.03% 🔽)	3.3 s (+4.51% 🔺)	7 s
ECIES encryption	22.88 KB (0%)	458 ms (0%)	453 ms (-33.82% 🔽)	911 ms
Symmetric encryption	22.42 KB (0%)	449 ms (0%)	592 ms (-15.19% 🔽)	1.1 s
DNS discovery	73.67 KB (0%)	1.5 s (0%)	2.2 s (+20.9% 🔺)	3.7 s
Peer Exchange discovery	75.37 KB (0%)	1.6 s (0%)	1.7 s (-27.37% 🔽)	3.2 s
Local Peer Cache Discovery	68.99 KB (0%)	1.4 s (0%)	1.4 s (-17.48% 🔽)	2.8 s
Privacy preserving protocols	39.97 KB (0%)	800 ms (0%)	1.4 s (-19.7% 🔽)	2.2 s
Waku Filter	20.11 KB (-0.03% 🔽)	403 ms (-0.03% 🔽)	515 ms (+22.71% 🔺)	917 ms
Waku LightPush	115.41 KB (-0.11% 🔽)	2.4 s (-0.11% 🔽)	2.2 s (-21.87% 🔽)	4.5 s
History retrieval protocols	116.05 KB (+500.75% 🔺)	2.4 s (+500.75% 🔺)	2.5 s (+713.01% 🔺)	4.8 s
Deterministic Message Hashing	4.96 KB (0%)	100 ms (0%)	48 ms (+39.99% 🔺)	147 ms