op-node: catch up L2 sequencing based on time, not L1 origins

[protolambda]

Description

Make sure to produce a L2 chain up to and including the latest wall clock timestamp. The L1 origin that we adopt doesn't matter in the catchup logic. When producing the block, and older L1 origin can be selected based on the conf depth, but the L2 chain should still be produced.

Tests

Fix based on alpha-1 testnet syncing occurence. Can extend testing in e2e for this later.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 46a7936

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mergify]

This PR changes implementation code, but doesn't include a changeset. Did you forget to add one?

[tynes]

Any plan for this PR to be actually merged?

[protolambda]

@tynes yes, this is an important fix, thank you for reminding me.

[trianglesphere]

lgtm

[mergify]

This PR has been added to the merge queue, and will be merged soon.

[mergify]

This PR is next in line to be merged, and will be merged as soon as checks pass.

[mergify]

Hey @protolambda, this pull request failed to merge and has been dequeued from the merge train. If you believe your PR failed in the merge train because of a flaky test, requeue it by commenting with @mergifyio requeue.
More details can be found on the Queue: Embarked in merge train check-run.