Context

Similar to what I previously did for smart rollups. This would be really facilitate my life if I can chose the smart contract address. With this merge request I can on testnets:

1. Runs the EVM rollup with a fixed sr1.
2. Deploy a FA1.2 contract with a fixed KT1
3. Deploy a bridge contract between the FA1.2 contract and the EVM rollup with a fixed KT1.

Please let me know if there a potential issues with that.

Manually testing the MR

Write a custom protocol parameter with and put a "hash" : "KT1..." for the bootstrap contract.

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR