Enable on conflation app to recreate Shanghai execution proofs

[gauravahuja]

This PR implements issue(s) #

Checklist

• I wrote new tests for my new core changes.
• I have successfully ran tests, style checker and build against my new changes locally.
• I have informed the team of any breaking changes if there are any.

---

Note

Run only the conflation/block creation flow starting from block 8814441, disabling proof aggregation/blob compression and all L1 submission/finalization services.

• Conflation:
  • Force starting point: set lastProcessedBlockNumber to 8814441uL (pre-Shanghai) instead of resumeConflationFrom(...).
  • Startup/Shutdown: start() now only starts blockCreationMonitor; stop() only stops blockCreationMonitor.
  • Disable surrounding flows: comment out DB cleanup, proofAggregationCoordinatorService, deadlineConflationCalculatorRunner, and blobCompressionProofCoordinator.
• L1 App:
  • Startup/Shutdown: start() now only starts conflationApp (via toSafeFuture()); stop() only stops conflationApp.
  • Disable L1-related services by commenting out starts/stops for l1FinalizationMonitor, Shomei handler, blob submission, aggregation finalization, message anchoring, L2 gas pricing, and L1 fee history cache.

^{Written by Cursor Bugbot for commit 34f56db. This will update automatically on new commits. Configure here.}

[cursor]

Bug: Hardcoded Block Number Causes Incorrect Behavior

The lastProcessedBlockNumber is hard-coded to 8814441uL with a devnet-specific comment, replacing the dynamic resumeConflationFrom logic. This committed debugging code may cause incorrect behavior in non-devnet environments by ignoring the actual system state.