feat: F3 e2e lifecycle

[karlem]

Closes #1441 and #1442

---

Note

High Risk
Touches consensus-critical topdown finality, genesis bootstrapping, and on-chain F3 light client state encoding; misconfiguration or state transition bugs could stall syncing or lead to incorrect finality/proof handling.

Overview
Enables an F3 proof-based topdown finality path alongside legacy vote-based topdown, with startup now selecting mode based on config+genesis consistency and bootstrapping a persistent proof cache + optional proof generator service.

Updates the f3-light-client actor to store the power table in a HAMT (exposing power_table_root), track processed_instance_id with monotonic/skip guards, and adjust constructor/update/get APIs and tests accordingly. Genesis-from-parent now fetches the F3 certificate to derive base_epoch + base_epoch_eth_block_hash, and parses power values as big integers (encoded big-endian bytes) instead of u64.

Adds fendermint_vm_evm_event_utils and a new interpreter event_extraction module to decode Solidity event proofs (NewTopDownMessage, NewPowerChangeRequest) from proof bundles using shared helpers; also refactors node topdown startup into service/topdown.rs, expands settings/default config docs for F3, and updates dependencies/lockfile to include new crates.

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[sergefdrv]

We should be able to initialize the cursor from the base tipset's storage commitment (used only as parent here), which is the same as the last tipset in the previous cert (used as child there). WDYT?

[sergefdrv]

As a workaround, maybe we could fetch parent tipsets (which are not very useful anyway) right in generate_proof_for_epoch, call it for the base tipset, get the nonces from the resulting proof bundle and discard the proof. Perhaps, we can do this only once and then maintain the cursor in ProofGeneratorService struct.

[karlem]

I think the best way here is to store it on L2 ledger...