OpenSSF Best Practices Badges - Enforce coding style(s)

[FredFousPro]

In order to fully validate the silver level of OpenSSF Best Practices Badges for our project, we have to investigate on the requirement above and see how to meet it.

Here is the requirement to meet:
The project MUST automatically enforce its selected coding style(s) if there is at least one FLOSS tool that can do so in the selected language(s). [coding_standards_enforced]
This MAY be implemented using static analysis tool(s) and/or by forcing the code through code reformatters. In many cases the tool configuration is included in the project's repository (since different projects may choose different configurations). Projects MAY allow style exceptions (and typically will); where exceptions occur, they MUST be rare and documented in the code at their locations, so that these exceptions can be reviewed and so that tools can automatically handle them in the future. Examples of such tools include ESLint (JavaScript), Rubocop (Ruby), and devtools check (R).

Here is the questionnaire :
https://bestpractices.coreinfrastructure.org/en/projects/5925?criteria_level=1

[Sander3003]

Todo:

• Write documententation how to set the default settings.
• Add Intellij profile to the repository / it would be nice if the check can be platform independent (e.g. https://checkstyle.sourceforge.io/config_design.html)
• Investigate the Sonarcloud settings

Background:
ESlint is already in place for the front-end.
Sonarcloud already checks the code style with best practices