Allow option to start logging the whole path of

### Use Case

To start logging the whole path the metric went through while processing, during test runs:

input: influxdb_v2_listener
--initial_metric
processor: regex
--modified_metric
processor: rename
--renamed_metric
aggregator: basicstats
--aggregated_metric
output: file
--output_metric

### Expected behavior

During test run start logging every step a metric went through from input to output and also what was the state of the log after each step.

### Actual behavior

There is no way to check which processors/aggregators were applied for a specific metric

### Additional info

_No response_

Start by tracing Telegraf's metric processing path during test runs, since the issue does not name specific files or tests. Determine where per-metric processor, aggregator, input, and output state could be recorded, then define an option that logs each step and its state from input through output. Done means a test run can show the complete path for a selected metric.

Written by the indexing model from the issue text.