[L2 Testnet Tutorial] update the L1 contract deployment section

[sbvegan]

Description

The first step to updating the L2 testnet tutorial is to fix how we advise developers on how to deploy the L1 smart contracts using op-deployer. There are a few places in the docs that deal with deploying the L1 contracts:

• https://docs.optimism.io/builders/chain-operators/deploy/smart-contracts
• https://docs.optimism.io/builders/chain-operators/tutorials/create-l2-rollup#deploy-the-l1-contracts
• https://docs.optimism.io/builders/chain-operators/deploy/smart-contracts

Acceptance criteria

• Each page listed in the description has a uniform description on how to deploy the L1 smart contracts

User stories

• As someone using the documentation to deploy the L1 smart contracts I am able to use the op-deployer tool to easily handle these deployments.

Resources and support

• The op-deployer docs are up to date

Action items

1. Update the OP Stack smart contract deployment documentation with the following changes:
   1. Move the warning callout at the top to just above the Deployment configuration header.
   2. Update the warning callout to say, "The following deployment information is the legacy method for deploying the OP Stack L1 contracts. We do not recommend you use this method. They're left here for historical context."
   3. Move the light bulb callout to the top of the page and change it to an informational callout. Change "should" to "must".
   4. Add the instructions included in the op-deployer documentation here
2. Update the L2 testnet tutorial - deploy the l1 contracts with the steps from the op-deployer docs.

[Red-Pandaz]

Regarding "Update the L2 testnet tutorial - deploy the l1 contracts with the steps from the op-deployer docs."- I have been unable to get op-node running with the current instructions after deploying the L1 contracts with op-deployer.

To be more specific, the version of op-node in the tutorials/chain branch of the Optimism monorepo is not up to date and does not support the l1.beacon flag.

Running
./bin/op-node \ --l2=http://localhost:8551 \ --l2.jwt-secret=./jwt.txt \ --sequencer.enabled \ --sequencer.l1-confs=5 \ --verifier.l1-confs=4 \ --rollup.config=./rollup.json \ --rpc.addr=0.0.0.0 \ --p2p.disable \ --rpc.enable-admin \ --p2p.sequencer.key=$GS_SEQUENCER_PRIVATE_KEY \ --l1=$L1_RPC_URL \ --l1.rpckind=$L1_RPC_KIND
returns
Application failed message="failed to setup: unable to create the rollup node config: ecotone upgrade scheduled but no beacon endpoint is configured".
Adding the flag returns
Incorrect Usage: flag provided but not defined: -l1.beacon.

Is there a workaround for this? If not, either the tutorials/chain branch should be updated or the instructions should be revised to prompt the user to use a more up-to-date branch/release.

[krofax]

@sbvegan This is ready for review.

[salman01zp]

@Red-Pandaz did you get a workaround this ? I am facing similar issue.