feat(protocol-kit): Predict Safe address improvements

[yagopv]

What it solves

Resolves #968

How this PR fixes it

• We are adding a new method to the protocolKit instance

const contractInfo = protocolKit.getContractInfo("0xContractAddress")

it returns the following:

{
  version: "1.3.0"
  type: "eip155"
  contractName: "safeSingletonVersion"
}

We can check the specific safe version and deployment type of a Safe contract Ethereum address

• We are adding a new optional property to the SafeDeploymentConfig

{
  saltNonce?: string
  safeVersion?: SafeVersion
  deploymentType?: DeploymentType // New "canonical", "eip155" or "zksync"
}

When using this new property with the predictedSafe, the protocolKit initialisation step will use the specified deployment type

const protocolKitGnosis = await Safe.init({
  provider: 'https://rpc.gnosischain.com',
  predictedSafe: {
    safeAccountConfig: {
      owners: ['0xOwnerAddress'],
      threshold: 1
    },
    safeDeploymentConfig: {
      safeVersion: '1.3.0',
      saltNonce: '0x123',
      deploymentType: 'eip155'
    }
  }
})

• Not related to the concrete issue => We are moving the SafeProvider.init method params to an options object

[coveralls]

Pull Request Test Coverage Report for Build 11052216509

Details

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 76.73%

---

Totals
Change from base Build 11030325314:	0.0%
Covered Lines:	777
Relevant Lines:	948

---

💛 - Coveralls