TrieDBMutBase added: no commit on drop

[michalkucharczyk]

This PR adds an option to prevent TrieDBMut from committing implicitly on drop.

This PR extends the TrieDBMut implementation to provide better control over when changes are committed to the database.

Changes:

• commit_on_drop flag added to TrieDBMut,
• Added without_commit_on_drop method to TrieDBMutBuilder which configures the builder to create a non-commiting TrieDBMut instance for cases where commit on drop is undesired.

Part of: paritytech/polkadot-sdk#6020

[lexnv]

nit: I generally prefer having a dedicated "chore" release PR with no/minimal changes, we'll also need to add this PR to the trie-db changelog 🤔

[michalkucharczyk]

well, just copied the "modus operandi" from some other commit in this repo :), which makes a change and bumps version.

[lexnv]

I think that works too, proly need a few more bumps? 🤔

[michalkucharczyk]

@lexnv

Yes, I can do it. Not really needed as they are mainly tests/benchmarks, but I will bump and publish these crates.
See: c682c3a

[lexnv]

LGTM! I think we can add the release to a dedicated PR and tiny question around the root ++ commit op 🙏

[lexnv]

Looks good! 🙏

[bkchr]

Some nitpicks. Otherwise should be fine as it doesn't change the default behavior.

[michalkucharczyk]

Uploaded crates:

Uploaded trie-db-test v0.31.1 to registry `crates-io`
Uploaded trie-bench v0.42.1 to registry `crates-io`
Uploaded reference-trie v0.29.2 to registry `crates-io`
Uploaded trie-db v0.31.0 to registry `crates-io`

New tags:

 * [new tag]         reference-trie-v0.29.2 -> reference-trie-v0.29.2
 * [new tag]         trie-bench-v0.42.1 -> trie-bench-v0.42.1
 * [new tag]         trie-db-test-v0.31.1 -> trie-db-test-v0.31.1
 * [new tag]         trie-eip1186-v0.5.1 -> trie-eip1186-v0.5.1
 * [new tag]         trie-eip1186-test-v0.7.1 -> trie-eip1186-test-v0.7.1
 * [new tag]         trie-db-v0.31.0 -> trie-db-v0.31.0