ci: add script and dockerfiles checks to github build action

[Synar]

Close #9650

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 42.48%. Comparing base (e67214e) to head (2e26358).
Report is 3 commits behind head on dev.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@             Coverage Diff              @@
##                dev    #9658      +/-   ##
============================================
- Coverage     42.49%   42.48%   -0.02%     
  Complexity     2272     2272              
============================================
  Files          1312     1312              
  Lines        105608   105608              
  Branches       3305     3305              
============================================
- Hits          44878    44867      -11     
- Misses        58777    58788      +11     
  Partials       1953     1953              

Flag	Coverage Δ
core	74.95% <ø> (ø)
editoast	73.68% <ø> (-0.04%)	⬇️
front	18.79% <ø> (ø)
gateway	2.18% <ø> (ø)
osrdyne	3.28% <ø> (ø)
railjson_generator	87.49% <ø> (ø)
tests	86.74% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[Synar]

When introducing a capitalization difference that would generate a docker warning the CI correctly identifies it and fails

[Synar]

Welp looks like my test on the core dockerfile automatically requested your review @eckter , sorry for that ^^

[Synar]

The shellcheck test also seems to be working properly. Sadly it looks like we did not need to simulate a warning this time...
Linting fixes coming as a second commit, though perhaps we will need to ignore some .

[Khoyo]

You clearly need to exclude /core/gradlew. It's a generated wrapper for gradle.

[Synar]

What severity do we care about for shellcheck? Do we want to catch styling and info messages, or only warnings and errors?

I guess we could keep the default (catching all severity levels) unless and until it becomes an issue

[Khoyo]

Missed adding names:

• check_reuse_compliance
• end_to_end_tests
• integration_tests
• check_osrdyne
• check_gateway
• check_editoast_openapi
• check_editoast_lints
• check_editoast_tests
• check_core
• check_front_rtk_sync
• check_reuse_compliance
• check_infra_schema_sync

And additionally label_pr (not in build:yml)

[Synar]

Missed adding names:

* check_reuse_compliance

* end_to_end_tests

* integration_tests

* check_osrdyne

* check_gateway

* check_editoast_openapi

* check_editoast_lints

* check_editoast_tests

* check_core

* check_front_rtk_sync

* check_reuse_compliance

* check_infra_schema_sync

And additionally label_pr (not in build:yml)

Oups messed up my commit. I did not think to add a name to label_pr though, will do so.