chore: remove Lombard light-client configuration

[gjermundgaraba]

Summary

Removes the active Lombard Ledger mainnet and testnet light clients from the eureka-ops deployment configuration.

Changes

• Remove the ledger-mainnet-1 light-client entry from the Ethereum mainnet deployment.
• Remove ledger-mainnet-1 from rateLimitedEscrows.
• Remove the ledger-testnet-1 light-client entry from the Sepolia deployment.
• Renumber the remaining mainnet client-4 entry from key 2 to 1.

Supersedes #21 so CI can access repository secrets.

[linear-code]

ECO2-477

[greptile-apps]

Greptile Summary

Removes the Lombard mainnet and testnet light-client entries, removes the mainnet Lombard escrow from rate-limit validation, and compacts the remaining mainnet client index.

• Deletes ledger-mainnet-1 and ledger-testnet-1 from deployment configuration.
• Removes ledger-mainnet-1 from rateLimitedEscrows.
• Renumbers client-4 from key 2 to key 1.

Confidence Score: 4/5

The validation blind spot for still-live Lombard clients and the mainnet escrow should be fixed before merging.

Removing these entries does more than disable active deployment configuration: it excludes existing on-chain clients and escrows from the repository's JSON-derived deployment, authority, and rate-limit checks.

Files Needing Attention: deployments/mainnet/1.json, deployments/testnet/11155111.json

Important Files Changed

Filename	Overview
deployments/mainnet/1.json	Removes a still-live migrated client and its escrow from JSON-derived deployment, authority, and hard rate-limit validation.
deployments/testnet/11155111.json	Removes the Lombard testnet client from the inventory used by deployment verification despite operational documentation still identifying its escrow.

_{Reviews (1): Last reviewed commit: "Merge remote-tracking branch 'origin/mai..." | Re-trigger Greptile}