Replace Linting and other static analysis tools with super-linter for CI

[ulises-jeremias]

Describe the feature

I propose switching our CI linting setup, which includes shellcheck, markdownlint, eslint, and others, to use super-linter exclusively for GitHub Actions. super-linter is a comprehensive and centralized linter that supports multiple languages, providing a unified linting experience.

Use Case

There are some benefits of super-linter:

• Unified Linting: super-linter supports a wide range of languages and linters, providing a unified linting solution for our GitHub Actions workflow.

• Easy Configuration: Simplifies configuration by having a single .github/linters configuration file.

• Consistent Output: Standardizes the output format for linting results across different languages and linters.

• Extensibility: Supports adding or customizing linters easily, making it adaptable to our specific requirements.

Proposed Solution

1. Configure super-linter:

   • Create or update the .github/workflows configuration file to specify the linters and configurations needed.

2. GitHub Actions Workflows:

   • Update the GitHub Actions workflow files to use super-linter for linting instead of the actual implementation

3. Testing:

   • Thoroughly test the linting process with super-linter in the GitHub Actions workflow to ensure it covers all relevant languages and provides accurate results. You can test this by submitting a PR

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Version used

latest

Environment details (OS name and version, etc.)

any