chore: Initial shape of centralized place for all Deployed contract addresses

[wdinau]

Problems to solve:
We would like one centralized place, publicly expose key contract addresses, so that we provide both confidence, trust and convenience to the builders and users in the community.
Currently, Immutable teams use Confluence or other alternatives to track deployed and verified contract addresses. They may or may not be up to date. No community members can see them from our public Docs. If they go to our chain exploer, since we deployed same thing multiple times, it's also not easy to see which ones are official.

Solution

• 1 json starts with most basic information about each contract that are useful in our ecosystem.
• Merge and publish this list ahead of Mainnet announcement.
• Short term will duplicate this information to a table on docs.immutable.com ZKevm Overview page.
• Long term, will automate pump this json info to where we need. Including potentially make an endpoint for this json to be available. Develop history tracking for it, and automation related to deployment.

Reviewers please:

• give feedback to the schema of this json. Keep it simple and powerful, did it miss any critical info?
• add, remove, modify Contracts that your team is responsible for --- instead of updating address in your team's Confluence, use here as source of truth.

[frankisawesome]

There's a few auxiliary contracts that do not have public facing/orderbook facing interfaces, and are only used by contracts through internal transactions, not sure how useful it is to make these public. Thoughts @immutable/traders ?