chore: monitor structure of the project

[vil02]

The goal of this change is to make the CI fail in case when some java files are not placed in the correct location (cf. #6288).

I realize that a python script might be an overkill at the first glance. I guess writing some smart shell script is possible, but in the long run, one could easily make the suggested solution more strict (do we have a naming convention of our tests? should we have one?).

Cf. the failing log.

• I have read CONTRIBUTING.md.
• This pull request is all my own work -- I have not plagiarized it.
• All filenames are in PascalCase.
• All functions and variable names follow Java naming conventions.
• All new algorithms have a URL in their comments that points to Wikipedia or other similar explanations.
• All new code is formatted with clang-format -i --style=file path/to/your/file.java

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.10%. Comparing base (1745d19) to head (41cd3d4).
⚠️ Report is 419 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##             master    #6291   +/-   ##
=========================================
  Coverage     74.10%   74.10%           
  Complexity     5345     5345           
=========================================
  Files           677      677           
  Lines         18639    18639           
  Branches       3618     3618           
=========================================
  Hits          13812    13812           
  Misses         4272     4272           
  Partials        555      555           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[siriak]

Looks good, thanks!