[ci] Fail CI if missing override instead of just warning

[ferdymercury]

Currently, many override warnings remain unnoticed since the gcc-problem-matcher of the GitHub CI does not work correctly, and it's also easy to forget those annotations if you do not visit the "Files changed" tab.

If some devs later use dev=ON and testing=ON, this leads to failures for compilers that auto-enable -Winconsistent-missing-override.

To prevent this, we enable the suggest-override warning in the build of debian with dev=ON instead of in the one from alma, this way we are sure of always failing if some does a PR that forgets an override, forcing pull-requesters to fix their issues before merging.

Within this PR: also fix missing overrides uncovered by turning ON this flag in the dev=ON build.

[ferdymercury]

@pcanal I see a fatal error: module file '/github/home/ROOT-CI/build/lib/MultiProc.pcm' is out of date and needs to be rebuilt: module file out of date in https://github.com/root-project/root/actions/runs/15753057412/job/44402174612?pr=19092

[github-actions]

Test Results

    20 files      20 suites   3d 8h 43m 57s ⏱️
 3 091 tests  3 091 ✅ 0 💤 0 ❌
60 219 runs  60 219 ✅ 0 💤 0 ❌

Results for commit 0c8d97e.

♻️ This comment has been updated with latest results.

[linev]

Yes, this is also my observation.
But normally such error appears only when converting from old Makefiles to cmake-based testing.
Then normal compiled options are applied - and on some CI platforms warnings automatically causing errors.

[ferdymercury]

Thanks @linev for the feedback.

Btw, do you approve the changes in roottest/io ?

[linev]

Btw, do you approve the changes in roottest/io ?

For this part clearly Philippe @pcanal is responsible

[pcanal]

Thank you!