Multiple processors not configurable through yaml

There are multiple processors that are not configurable through yaml.
With shortly clicking through I found clone, convert, default, starlark

They all have something like the following as syntax when converted to toml
```
[[processors.converter]]
[processors.converter.tags]
string = [
"application_identifier",
"app_uuid",
"pod",
"endpoint_id",
"block_id",
"field_*",
]
```

But they incorrectly get converted to something like

```
[[processors.converter]]
[[processors.converter.tags]]
string = [
"application_identifier"
"app_uuid",
"pod",
"endpoint_id",
"block_id",
"field_*",
]
```

That is because multiple other processors use the double [ syntax on the second level.

Start by locating the Helm chart template or entry point that converts processor configuration to TOML. Compare the clone, convert, default, and starlark processors, focusing on the nested tags structure shown in the issue. Done means each processor's YAML configuration produces the correct single-table TOML structure rather than an extra array-of-tables level.

Written by the indexing model from the issue text.