Add Biconomy's Bundler to prool

[TheDivic]

In the SDK We’ve started using prool for testing (soon to be merged in the nexus/feat branch), which allows us to test on local Anvil networks instead of public testnets. This has significantly improved our SDK testing process by enabling us to deploy multiple instances of a bundler (currently using Alto) to different ephemeral Anvil nodes. We would love to transition to using our own bundler instead of Alto, but we are now somewhat tied to Prool because of the advantages it gives us versus testing on public testnets.

Our competitors are supported by prool

On a related note, jxom from Wevm (main author of prool) recently reached out to discuss making our bundler accessible via a binary or a command similar to yarn. There’s more context about this discussion here and in a Wevm <> Biconomy Telegram channel that you can be added to if required

Given that the work jxom requested aligns closely with what we need in the SDK to properly test our bundler, it would be fantastic if you could adjust your current definition of “done” for the EPV7 bundler work to include a PR into the Prool package. This change would benefit us by allowing us to leverage the bundler in our SDK testing, while also providing you with rigorous testing for the bundler from the SDK, and potentially benefiting the broader industry by making our bundler available via Prool too.

[veljkovranic]

Our bundler is dockerised and as such can be used for spawning dev environment. However, that requires quite a few steps (a few config files, encryption of one of the) and it takes 4 additional images (Mongo, Redis, RabbitMq, Centrifugo) as dependencies in order to run.

That shouldn't be the case for prool, since this is a fully fledges SaaS product, so trimming down this dependencies and simplifying config should be done prior to tacking this issue.