check if the Safe Account is 4337 compatible

[DaniSomoza]

What it solves

Resolves #720

How this PR fixes it

• The Safe uses v1.4.1 version.
• Safe has the 4337 module enabled.
• Safe has the 4337 fallback handler enabled.

How to test this PR

  // 1) Initialize pack with the Safe Address
  const safe4337Pack = await Safe4337Pack.init({
    ethersAdapter,
    rpcUrl: RPC_URL,
    bundlerUrl: BUNDLER_URL,
    options: {
      safeAddress
    }
  })

You can use this Safes in Sepolia to test this checks:

• 0x9534Bc54EB95975DaF2Dbc74ff945f0DB9810043: Safe with 1.3.0 version, this version is not compatible with 4337.
• 0xfC82a1e4A045a44527e8b45FC70332C8F66fc32B: Safe with 1.4.1 version but no 4337 Module attached.
• 0xA6FDc4e18404E1715D1bC51B07266c91393C6622: Safe with 1.4.1 version and 4337 Module attached but no 4337 fallback handler attached.
• 0xB4510553D7ecD3F2A3170ce2cD16A21853D07b9C: Safe 4337 Compatible (1.4.1 version, 4337 Module and 4337 fallback handler attached)