fix: Parsers do not have to be in seperate files

On the "Parsers" page for the v4.0 documentation, it states:

> You can define parsers either directly in the main configuration file
> or in separate external files for better organization.

But on the "Configuring parsers" section, subsection "Parser Configuration File"[2],
it says:

> All parsers must be defined in a parsers file, not in the Fluent Bit
> global configuration file.

Those seem like contradictory statements. I think the truth is that
parsers may be defined in the main global configuration file, behavior
which I think is supported since v3.2

[1] - https://docs.fluentbit.io/manual/administration/configuring-fluent-bit/yaml/parsers-section
[2] - https://docs.fluentbit.io/manual/data-pipeline/parsers/configuring-parser#parsers-configuration-file

Author: lelandbatey

pipeline/parsers/configuring-parser.md

@@ -45,7 +45,7 @@ Multiple parsers can be defined and each section has it own properties. The foll
 
 ## Parsers configuration file
 
-All parsers must be defined in a parsers file, not in the Fluent Bit global configuration file. The parsers file exposes all parsers available that can be used by the input plugins that are aware of this feature. A parsers file can have multiple entries, like so:
+All parsers may be defined in a parsers file. The parsers file exposes all parsers available that can be used by the input plugins that are aware of this feature. A parsers file can have multiple entries, like so:
 
 {% tabs %}
 {% tab title="parsers.yaml" %}