Reviewdog container image #9082

[mhitza]

Creates a new workflow step (and container) in order to be able to use reviewdog to check code quality of php/twig/symfony based projects.

This has an opt-in mechanism, via a new reviewdog top-level property in the schema.

Removes configuration parts, such as yamllint due to large amounts of false positives, as well as switching to newer/alternative tools where the old ones are deprecated (eg twigcs-fixer -> twig-cs-fixer)

Types of changes

• feat: non-breaking change which adds new functionality
• fix: non-breaking change which fixes a bug or an issue
• chore(deps): changes to dependencies
• test: adds or modifies a test
• docs: creates or updates documentation
• style: changes that do not affect the meaning or function of code (e.g. formatting, whitespace, missing semi-colons etc.)
• perf: code change that improves performance
• revert: reverts a commit
• refactor: code change that neither fix a bug nor add a new feature
• ci: changes to continuous integration or continuous delivery scripts or configuration files
• chore: general tasks or anything that doesn't fit the other commit types

• Breaking change: fix or feature that would cause existing functionality to not work as expected

Checklist

• I have read the Contributing doc
• I have read the Creating and reviewing pull requests at LinkORB guide doc
• Lint and unit tests pass locally with my changes
• I have added/updated necessary documentation in the README.md or doc/ directories (if appropriate)