Improve prepare-node-config for Orbit Rollup Deployment

[dindonero]

Improve prepare-node-config for Orbit Rollup Deployment

Overview

This PR improves the prepare-node-config functionality to ensure smoother deployments of an Orbit rollup using the SDK examples. These updates enhance configuration clarity, usability, and compatibility across the Orbit ecosystem.

Key Improvements

1. Configurable Chain Name in .env

   • Enables customization of the chain name at the environment configuration level for better flexibility in deployments.

2. Generation of orbitSetupScriptConfig.json

   • This file is a critical component for integrating Orbit chains across various tools:
     • Used by the setup.js script during deployment.
     • Required in the bridge UI for adding custom Orbit chains.
     • Simplifies arbitrum-sdk integration via example configurations. Registering a new custom network from the orbitSetupScriptConfig.json example can be found in the bridge UI repo.

3. RPC Endpoint Handling

   • PARENT_CHAIN_RPC is now stored in nodeConfig.json and orbitSetupScriptConfig.json.
   • This ensures that user-provided RPC endpoints are prioritized over defaults, avoiding timeouts or connection issues.

4. Consistent Naming

   • Renamed node-config.json to nodeConfig.json for uniformity with other file naming conventions.

Reasoning

These changes address challenges in the deployment process, such as:

• Timeout issues with default RPC endpoints.
• Improved usability and cross-compatibility by aligning configurations across tools.
• Enhanced developer experience with more predictable and standardized file naming.

---

Relevant Links

• Setup Script (setup.js)
• Bridge UI Configuration Example

Summary of Changes

• Added configurable chain name in .env
• Generates orbitSetupScriptConfig.json for deployment use
• Fixed: PARENT_CHAIN_RPC now stored in nodeConfig.json and orbitSetupScriptConfig.json
• Renamed node-config.json to nodeConfig.json for consistency

[dindonero]

Please review lines 97 and 100. Verify if the outputs for minL2BaseFee and utils are correct.