Formalize and repackage IBS, Commitement and Unwind tracing

See: https://github.com/erigontech/erigon/pull/17783

We currently have adhoc experimental tracing in [common/dbg/experiments.go](https://github.com/erigontech/erigon/pull/17783/files/2f2c33ee0b80e68af41322208f183596fc0d3701#diff-2473dae35ff7403094183187678c41fe90225faf5cf1423f4a8fb62a62bf951c).

These are generally useful for tracking down state root mismatches, reciept hash mismatches etc where the standard logging just reports the top level error.

The issue with this type of tracing is that to be useful it is also generally verbose and even at a trace logging level will overwelm the standard log files.

At the moment the strategy is to log this to the console & switch it on and off via deb environment variables.

As this is generally useful it needs to have an API developed which allows:

1. Specification of output location
2. Conditional switching on and off of featires - both externally and via an internal API for tests & web API for client usage.
3. Movement of specific traces into housting pakages (e.g. kv to avoid code duplication)