ERC-4377 support

[tuler]

📚 Context

Account Abstraction (ERC-4377) is an important feature of EVM networks, providing several usability improvements.

Cartesi applications are already compatible with Account Abstraction. There is no change necessary to a Cartesi application to support ERC-4377. Advance requests arrive normally to a Cartesi backend.

But on the other hand the frontend of an application needs to implement support to ERC-4377.
When using a testnet there are several service providers that offer the necessary infrastructure to implement ERC-4377 (Alchemy, ZeroDev, Biconomy, Stackup, etc)

But on a local development environment, using the Cartesi CLI we need to provide that support.

✔️ Solution

The required infrastructure for ERC-4377 includes the following:

• several smart contracts deployed to the local anvil instance. This includes core contracts and popular smart wallets factories.
• a bundler server
• a paymaster server

Pimlico provides documentation about how to run a ERC-4377 infrastructure locally. It consists of deploying a set of smart contracts, and running a local instance of alto and a mock paymaster.

If the developer wants to use a passkey signer he will also need a passkey server. One implementation is provided by ZeroDev.

Alto is one popular implementation of a bundler. It's written in typescript, and already has a docker image part of its release process.

📈 Subtasks

• deploy ERC-4377 support contract to the devnet
• add the bundler to the SDK
• add the paymaster to the SDK
• add the bundler to the cartesi run
• add the paymaster to the cartesi run

🎯 Definition of Done

• use the CLI bundler and paymaster with Cartesi applications frontends.