Create storage subcommand supporting ERA1 import/export format

[garyschulte]

Description

In support of dropping chain history, besu will need to support the ERA1 format for chain history pre-merge. ERA1 data can be used to full sync the chain for specific cases like archive nodes. Creating a subcommand that imports and ERA1 data will provide the functionality necessary to scan and read ERA1 files.

For other chains which do not already have ERA1 data generated, or wish to leverage ERA1 for other reasons, we should also implement an export subcommand which implements an accumulator and file writer. This also will serve to cross-verify the mainnet pre-merge ERA1 exports that have been generated by other execution clients.

Acceptance Criteria

• ERA1 format support for reading
• ERA1 accumulator for writing
• Storage subcommands for importing and exporting ERA1 files from besu chain data