fix(parsers.csv): Remove direct checks for the parser type

[srebhan]

• Updated associated README.md.
• Wrote appropriate unit tests.
• Pull request title or commits are in [conventional commit format]

partially resolves #11820

This PR introduces a new error (ErrNotEnoughData) for parsers that need to consume more data to output metrics. This is the case for CSV when fed linewise with skipping rows, metadata or other headers involved.

As a consequence, we can remove the direct check for the CSV parser in inputs.tail and inputs.directory_monitor and open the possibility for other parsers to also use this error.

[telegraf-tiger]

Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip.
Downloads for additional architectures and packages are available below.

☺️ This pull request doesn't significantly change the Telegraf binary size (less than 1%)

📦 Click here to get additional PR build artifacts

Artifact URLs

DEB	RPM	TAR GZ	ZIP
amd64.deb	aarch64.rpm	darwin_amd64.tar.gz	windows_amd64.zip
arm64.deb	armel.rpm	darwin_arm64.tar.gz	windows_i386.zip
armel.deb	armv6hl.rpm	freebsd_amd64.tar.gz
armhf.deb	i386.rpm	freebsd_armv7.tar.gz
i386.deb	ppc64le.rpm	freebsd_i386.tar.gz
mips.deb	riscv64.rpm	linux_amd64.tar.gz
mipsel.deb	s390x.rpm	linux_arm64.tar.gz
ppc64el.deb	x86_64.rpm	linux_armel.tar.gz
riscv64.deb		linux_armhf.tar.gz
s390x.deb		linux_i386.tar.gz
		linux_mips.tar.gz
		linux_mipsel.tar.gz
		linux_ppc64le.tar.gz
		linux_riscv64.tar.gz
		linux_s390x.tar.gz
		static_linux_amd64.tar.gz

[reimda]

This fixes the bug caused by the last two wrapped parsers listed in #11820. It's a fix for the regression in 1.24.0 and should be included in 1.24.1.

When we have more time, we should revisit the approach of using a parser specific error (originally parsers.ErrNotEnoughData in this PR but now named parsers.ErrEOF). If the input plugin is always going to ignore the error, it would be simpler if the parser didn't return an error to begin with. Maybe parsers whose Parse methods calls their own ParseLine method need it?

If we do decide parsers.ErrEOF is needed, we should check the other parsers besides csv and update them to use it. For example, xml could return it if it hasn't received data including a closing tag, and influx could use it when it has received part of a line but not the end of line character.