Define moodle-cs own standard, towards better coding

[stronk7]

Here we are introducing the phpcs.xml.dist file that will guide our coding style within moodle-cs.

• It scans all the code but vendor and fixtures directories.
• It's the complete PSR12 standard but allowing single-line function declarations to have the opening curly bracket in the same line.
• With line length adjusted to 132 / 180.
• And a few more sniffs, not part of the PSR12, but good for readability (hopefully non-controversial):
  • && and || logical operators.
  • Short array syntax.
  • Space after commas.
  • Comma at the end of multi-line arrays.
  • PHPCompatibility standard to check for >=7.4 (with an exception about T_ENUM false positives).

And that's it!

Then, apart of the above, small adjustments to the composer.json and .gitignore files.

[stronk7]

Created as draft, soon I'll add the BIG commit adapting all the code to the above.

Let's discuss if there is anything else to add / remove in the configuration.

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 99.66667% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 97.29%. Comparing base (e2fdd2f) to head (313e171).

Files	Patch %	Lines
moodle/Sniffs/Files/MoodleInternalSniff.php	97.82%	1 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #117 +/- ## ============================================ + Coverage 97.15% 97.29% +0.13% Complexity 655 655 ============================================ Files 29 29 Lines 1864 1957 +93 ============================================ + Hits 1811 1904 +93 Misses 53 53 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[stronk7]

Ok, I've added 3 more commits, apart from the initial one, described above. This is a summary of all them:

1. Define the phpcs.xml.dist file, that configures the style to be used with moodle-cs.
2. Apply all the changes in code base towards being compliant with the style defined & agreed.
3. Modify the testing API to be, also compliant with the style.
4. Cover everything @ GHA with a new step that will check for compliance. Plus update changelog.

And that's all. I think this is now complete and can be considered for merging.

Ciao :-)

[stronk7]

Thanks!