docs: plugin README code blocks don't match their fenced language (tracking)

[jstirnaman]

Summary

Adding code-block linting to the InfluxData docs site (which generates the
published plugin docs from these READMEs) surfaced a set of plugin READMEs whose
fenced code blocks declare a language that doesn't match the content. A few are
genuine errors a reader could copy-paste; most are fence-language mismatches that
produce misleading highlighting and fail JSON validation downstream.

This issue tracks the cleanup. For config blocks, changes are made in each
plugin's sample.conf and the README is regenerated with make docs, per the
guidance on #18830. The single bundled PR #18830 is superseded by the per-plugin
PRs below.

Genuine errors (PRs)

Each fix was verified by loading the config in Telegraf 1.39.1.

• docs(processors.converter): fix unterminated string in timestamp example #19202 processors.converter — unterminated string in timestamp example
• docs(inputs.opcua_listener): Use TOML comments in group example #19203 inputs.opcua_listener — C-style // comments are invalid in TOML
• docs(outputs.dynatrace): Use TOML comment in api_token example #19204 outputs.dynatrace — C-style // comment is invalid in TOML
• docs(inputs.postgresql_extensible): Fix invalid line-continued queries #19205 inputs.postgresql_extensible — invalid line-continued single-line strings
• fix(inputs.jti_openconfig_telemetry): Remove duplicate sensors key #19206 inputs.jti_openconfig_telemetry — duplicate sensors key (fixed in sample.conf)

Fence-language mismatches (issues)

• docs(inputs.bind): named.conf example is fenced as json #19190 inputs.bind — named.conf example fenced as json
• docs(inputs.ctrlx_datalayer): Source examples are fenced as json but aren't JSON #19191 inputs.ctrlx_datalayer — "Source" examples fenced as json
• docs(inputs.docker): label-filter examples are fenced as json but are TOML #19192 inputs.docker — label-filter TOML fenced as json
• docs(inputs.win_eventlog): truncated config fragment is fenced as toml #19193 inputs.win_eventlog — truncated fragment fenced as toml
• docs(outputs.azure_data_explorer): KQL function is fenced as json #19194 outputs.azure_data_explorer — KQL function fenced as json
• docs(outputs.clarify): signal example is fenced as json but isn't valid JSON #19195 outputs.clarify — signal example fenced as json
• docs(outputs.elasticsearch): REST request examples are fenced as json #19196 outputs.elasticsearch — REST request examples fenced as json
• docs(outputs.zabbix): JSON Lines output is fenced as json #19197 outputs.zabbix — JSON Lines output fenced as json
• docs(processors.lookup): illustrative JSON examples are fenced as json #19198 processors.lookup — illustrative JSON fenced as json
• docs(secretstores.http): illustrative JSON example is fenced as json #19199 secretstores.http — illustrative JSON fenced as json
• docs(serializers.splunkmetric): JSON examples are fenced as javascript #19200 serializers.splunkmetric — JSON examples fenced as javascript

Related

• docs(inputs.opcua_listener): event node_ids example uses outdated inline-array syntax #19189 inputs.opcua_listener — node_ids example uses outdated inline-array syntax
• Supersedes docs: fix code-block lint errors across plugin READMEs #18830