persist starlark state for more starlark types

### Use Case

#15170 added the ability for the starlark processor to persist the global state to the statefile between runs. This is very nice, but it can't store lists, dicts, tuples, or metrics to the state file which severely limits its usefulness. If you try any more complex type you get an error like `invalid starlark type *starlark.Metric` when it tries to write the state file.

My desired use case is similar to [the example](https://github.com/influxdata/telegraf/blob/e00bc7288c6f2f27e82ad741ced023c75ee4a998/plugins/processors/starlark/testdata/compare_metrics.star) for comparing a metric to the previous one. This doesn't work because it stores both a dict and a metric in the global state.

### Expected behavior

Starlark standard types (lists, dicts, tuples, and maybe also metrics) can be persisted to the statefile.

### Actual behavior

Error when persisting the plugin states.

### Additional info

_No response_

Start with the starlark processor's state persistence and the comparison example at plugins/processors/starlark/testdata/compare_metrics.star, then review the persistence change from #15170. Done means lists, dicts, tuples, and possibly metrics can round-trip through the statefile without the reported invalid starlark type error.

Written by the indexing model from the issue text.