op-deployer should display L1/L2 contract addresses

Users don't currently have a good way to see the contract addresses for a chain launched with op-deployer. This is useful when (for example) experimenting with or modifying the dispute game.

Originally raised here: https://github.com/ethpandaops/optimism-package/issues/84 Mark suggested that op-deployer print to stdout, but we may want to persist these addresses somewhere less ephemeral if we expect that people will want to reference them later.

This is a good dev delight request for op-deployer.

Start by locating the op-deployer command entry point and tracing how a launched chain reports deployment results. Compare the requested stdout output with the alternative of persisting addresses, using the dispute-game use case to clarify what users need to reference later. Done means L1 and L2 contract addresses are reliably available after deployment.

Written by the indexing model from the issue text.