fix: disable Werror=unused-values (IDFGH-14511)

[KaeLL]

It should warn, but not error out.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

	Warnings
⚠️	The Pull Request description looks very brief, please check if more details can be added.

👋 Hello KaeLL, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved, we synchronize it into our internal git repository.
4. In the internal git repository we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by 🚫 dangerJS against b895e87

[dobairoland]

@antmak @Lapshin Can you please take a look?

[igrr]

@KaeLL perhaps you could add, why do you think that the default behavior should be changed? If you want to allow this warning in your project, you can already do so, it doesn't seem to be necessary to change the default.

[KaeLL]

I believe having dead code or unused variables is reason for warnings, which is what this change is all about, but not build-breaking errors. For regular development, it breaks the usual "edit-compile-test-debug" cycle in exchange for absolutely nothing of positive that a warning wouldn't suffice. For production builds, the code will likely end up eliminated by the compiler anyways.
I guess the question is: why shouldn't this default be changed (back?)? I could be wrong or missing the whole picture.