[23858] Build with warnings as errors (backport #289)

[mergify]

Description

Just what the title says. We want builds to fail if there are warnings.

@Mergifyio backport 2.2.x 1.0.x

Contributor Checklist

• Commit messages follow the project guidelines.
• The code follows the style guidelines of this project.
• N/A: Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
• N/A: Any new/modified methods have been properly documented using Doxygen.
• Changes are backport compatible: they do NOT break ABI nor change library core behavior.
• Changes are API compatible.
• N/A: New feature has been added to the versions.md file (if applicable).
• Applicable backports have been included in the description.

Reviewer Checklist

• The PR has a milestone assigned.
• The title and description correctly express the PR's purpose.
• Check contributor checklist is correct.
• Check CI results: changes do not issue any warning.
• Check CI results: CI pass and failing tests are unrelated with the changes.

---

This is an automatic backport of pull request #289 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 9beec7e has failed:

On branch mergify/bp/1.0.x/pr-289
Your branch is up to date with 'origin/1.0.x'.

You are currently cherry-picking commit 9beec7e.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .github/workflows/reusable-ci.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   test/SimpleTest.cpp

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[MiguelCompany]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased