Create the batch collector account during bootstrap

[Mirko-von-Leipzig]

Node bootstrap creates the batch builder's collection account and saves it with its signing key in batch_builder_collection_account.mac in the node data directory. The file retains the account's creation seed for deployment. Genesis contains neither the collection account nor the wallet account.

The collector uses protocol's AuthTxFeeCollector to aggregate fee notes into a single P2ID note. Its state remains unchanged after deployment, so batch workers can use it concurrently. Authentication restricts use of the collector to the sequencer.

Part of #2501.

Changelog

[[entry]]
scope       = "node"
impact      = "added"
description = "Create the batch builder's collection account during node bootstrap."

[kkovaacs]

Looks good to me!

[Mirko-von-Leipzig]

Discussed offline, but it turns out this isn't required.

The accounts can instead be generated outside of genesis, and given to the sequencer. Both accounts will self-deploy on the first transaction involving them. And the transaction fee for each will be paid by the tx fees collected.

I'll amend these PRs. This does mean that there is an additional step for the sequencer to generate these accounts. Perhaps this can be part of bootstrapping - but this needs to be communicated well so that the accounts aren't lost.

[Mirko-von-Leipzig]

Superseded by #2568. Collector creation now uses the fee-collector create/deploy commands instead of node bootstrap. The remaining dependencies and account-file path helper are included in #2568.