feat(onramp-kit): Monerium integration

[yagopv]

What it solves

Resolves #376

How this PR fixes it

We are creating a new pack allowing users to integrate the Safe with Monerium. An example integration can be explored here

We are implementing our common interface providing the following methods:

• init(MoneriumPack) - Allow to initialize the kit with the MoneriumPack. We are going to provide the clientId and choose the Monerium environment to work with (sandbox or production)
• open(MoneriumOpenOptions) - We are going to start the Monerium flow in 3 ways:
  • Redirecting to the Monerium website and let the user login and provide access to the resources
  • By providing an authCode in the open options to exchange and get access to the resources
  • By providing a refreshToken in the open options to authenticate and get access to the resources
• subscribe(event, handler) / unsubscribe(event) - Once authenticated this methods allow the user to establish a socket connection with the Monerium servers and listen for order status changes
• close() - To cleanup the connection with Monerium

How to test it

• Follow the instructions to build the monorepo and the example
• Create an account in Monerium sandbox and then create an application for obtaining the clientId. Set the clientId in the .env file

Use Cases

1. Signin/Signup and link a 1/1 Safe. Should bind the Safe and autoexecute transactions as only the Web3Auth signer is required (Remember to send funds to the owner address as it will need them to autoexecute the txs)
2. Signin/Signup and link a 2/X Safe. Should bind the Safe and propose the signMessage transaction. Other signers should go to the Safe to sign
3. Send transactions (default to 1 EURe) between Monerium sandbox accounts and check they arrive. Same as 1) and 2) txs should autoexecute or require additional signers (In the Safe UI)

Read integration notes and attached videos to check how the example behaves

[dasanra]

Suggested change

	const isMessagePending = pendingTransactions.results.some((tx) => {
	if (
	// @ts-expect-error - dataDecoded should have the method property
	tx?.dataDecoded?.method === 'signMessage' &&
	// @ts-expect-error - dataDecoded should have the parameters array
	tx?.dataDecoded?.parameters[0]?.value === ethers.utils.hashMessage(message)
	) {
	return true
	}
	return false
	})
	const isMessagePending = pendingTransactions.results.some((tx) => (
	// @ts-expect-error - dataDecoded should have the method property
	tx?.dataDecoded?.method === 'signMessage' &&
	// @ts-expect-error - dataDecoded should have the parameters array
	tx?.dataDecoded?.parameters[0]?.value === ethers.utils.hashMessage(message)
	))