Update to allow for dynamically adding additional configuration and parser configuration files to fluent-bit.conf

This change adds two new variables to the default values.yaml for fluentbit:

config.parsersFiles - This value works like the existing config.extraFiles variable, however, it adds the filenames to the fluent-bit.conf file in the [SERVICE] section as Parsers_File <filename>. This allows for those files to be automatically imported without needing to override the config.service variable. This allows for additive changes without the need to modify, redeclare, or even really know about the existing config.service value. Since it is dynamically added as a parsers file, it is important that any files passed to this only contain valid fluentbit parser configurations or it will cause the service to error.

config.extraConfigFiles - This value works like the existing config.extraFiles variable, however, it adds the filenames to the fluent-bit.conf file as @INCLUDE <filename>. This allows for those files to be automatically imported without needing to override the config.service variable. This allows for additive changes without the need to modify, redeclare, or even really know about the existing config.service value. Since it is dynamically added as a file import, it is important that any files passed to this only contain valid fluentbit configuration file values (for instance [INPUT], [OUTPUT], etc.) or it will cause the service to error.

We have opted to create two new variables as opposed to modifying how the existing config.extraFiles is handled to ensure backwards compatibility with any existing deployments that make use of the config.extraFiles variable. As such, this update should be fully backwards compatible.