Github Action to use the config-file-validator (https://github.com/Boeing/config-file-validator https://github.com/Boeing/config-file-validator) to recursively

Github Action to use the config-file-validator (https://github.com/Boeing/config-file-validator https://github.com/Boeing/config-file-validator) to recursively scan the directory structure of a repo for config files and validate their syntax as part of a CI/CD pipeline. This is useful as a quick quality gate in your CI pipeline to validate that a syntax error was not introduced in the latest commit. Currently XML, JSON, YAML, INI, and TOML are supported with CSV, HCL, and Plist coming in the next release. Here's how to add it to your existing workflow: https://github.com/kehoecj/validate-configs-action/tree/main#standard-run https://github.com/kehoecj/validate-configs-action/tree/main...