Support ERC20 and ERC721 Bridging

[ggonzalez94]

While not core to the protocol, and more of an "application" concern, we agree that providing a bridge implementation for common token standards is important both for Taiko Alethia and for other rollups that want to use the stack.
Users of the stack can define if they want to use these implementations as the "canonical" bridge, or deploy their own.

• The implementations should use the SignalService for sending and verifying the messages
• We should support ETH + ERC token transfer(which shouldn't be that hard since Eth Bridging will be embedded into the SS) as the current implementation does.

Documentation for the current bridge implementation: https://docs.taiko.xyz/taiko-alethia-protocol/protocol-architecture/bridging

[ggonzalez94]

Some open questions:

• Should it differentiate between tokens native to the L1 and native to the L2? e.g. the OP stack on L1 if the token is native to L1 locks it, and if it is native to L2 burns it
• What type of tokens should it support? e.g. the OP stack does not support tokens with transfer fees, rebasing tokens, and tokens with blocklists.