feat: parallel deployment

[gzeoneth]

No description provided.

[Copilot]

Pull Request Overview

This PR enhances deployment tooling by enabling parallel contract deployments and updates corresponding tests for custom fee rollups.

• Adjusts gas extraction logic and assertion in end-to-end custom fee rollup tests.
• Introduces a SimpleMutex, nonce manager, and getNextNonce to coordinate non-CREATE2 deployments.
• Refactors scripts/deploymentUtils.ts to deploy multiple contracts in parallel and adds a helper for one-step prover deployment.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
test/e2e/customFeeRollup.ts	Fixed substring ranges for gas and extraGas extraction, added L1 gas usage assertion.
scripts/deploymentUtils.ts	Added mutex-based nonce/verification locks, getNextNonce, and rewrote sequential deploys as Promise.all.

Comments suppressed due to low confidence (4)

scripts/deploymentUtils.ts:31

• Add a brief doc comment above SimpleMutex explaining its behavior and intended use, so future maintainers understand the locking semantics.

class SimpleMutex {

scripts/deploymentUtils.ts:50

• Document the purpose of verifyLock, specifying that it serializes contract verifications to avoid rate limits or race conditions.

let verifyLock = new SimpleMutex()

scripts/deploymentUtils.ts:61

• [nitpick] The variable resolveVerifyLock represents the unlock function. Renaming it to releaseVerifyLock or unlockVerify would clarify its intent.

  const resolveVerifyLock = await verifyLock.lock()

scripts/deploymentUtils.ts:165

• Add a JSDoc comment for getNextNonce describing how it initializes and increments nonces per address, including lock behavior.

async function getNextNonce(signer: any): Promise<number> {

[Copilot]

The hard-coded substring indices (234, 298) are magic numbers. Extract these offsets into named constants or add comments explaining their origin for clarity.

[Copilot]

Similarly, the range (298, 314) is a magic number. Consider defining a constant or helper to document what these positions represent in the batch data.

[Copilot]

[nitpick] Consider extracting this receipt lookup into a helper function (e.g., getL1GasFromReceipt) to improve readability and reuse in other tests.

Suggested change

	const gasUsedForL1 = BigNumber.from(
	(
	await l2Provider.send('eth_getTransactionReceipt', [
	batchSpendingReportEvent.transactionHash,
	])
	).gasUsedForL1
	const gasUsedForL1 = await getL1GasFromReceipt(
	l2Provider,
	batchSpendingReportEvent.transactionHash

[Copilot]

Launching a large array of Promise.all deployments concurrently can overwhelm the RPC provider. Consider throttling concurrency or batching the promises.