feature: Implement hash preimage storage persistence

[garyschulte]

Description

Besu currently does not implement persistent preimage storage for Bonsai, and Forest only implements an in-memory cache for account and slot key preimages.

There are a couple existing features which require hash preimages are necessary such as debug_accountRange and reference test outputs, but these methods are currently limited to very small state tries for which an in-memory cache is sufficient.

In support of the verkle transition, besu needs to implement persistent preimage recording. In order to transition from patricia-merkle tries to verkle tries, besu needs to have the hash preimage to migrate the keys over to the new storage format. The transition details are still being worked out, but the need for preimage persistence and recording is essential.

Acceptance Criteria

• hash preimage persistence mechanism
• differentiate between account and storage preimages
• feature flag