Better support for EIP155 implementing chains

[jpalvarezl]

Context

In order to deploy safes in chains where the addresses are not the ones we get using the usual deterministic deployment, we need to manually input the factory and singleton addresses. For example:

yarn safe create --l2 --factory 0xC22834581EbC8527d974F8a1c97E1bEA4EF910BC --singleton 0xfb1bffC9d739B8D520DaF37dF666da4C687191EA

Even though these addresses are different, they are deterministically different, we can therefore somehow signal to use the different address when needed depending on the chain

Feature

Provide the means to signal that contract addresses for chains supporting EIP-155 should be used instead of the regular ones obtained from deterministic deployments.

Proposal

Something along the lines of:

yarn safe create --l2 --eip155

Could be a way to implement this from a user's perspective.