feat: recovery mode after permissionless batches

[jonastheis]

1. Purpose or design rationale of this PR

This PR implements a recovery mode after batches have been submitted permissionlessly in the context of permissionless batches. During permissionless mode the L2 network will not produce any valid/canonical L2 chain. Batches can be submitted by anyone directly to the L1.

This PR extends the L1 follower mode to be able to recover state from any given L1 block height --da.recovery.initiall1block and batch index --da.recovery.initialbatch to a given L2 end block --da.recovery.l2endblock, while overriding any existing local state of the node.

Additionally, it allows to re-sign the read blocks with --da.recovery.signblocks so that once the sequencer comes back online a valid canonical L2 chain can again be created from the permissionless committed batches.

2. PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
• ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
• docs: Documentation-only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

3. Deployment tag versioning

Has the version in params/version.go been updated?

• This PR doesn't involve a new deployment, git tag, docker image tag, and it doesn't affect traces
• Yes

4. Breaking change label

Does this PR have the breaking-change label?

• This PR is not a breaking change
• Yes