added [[maybe_unused]] in some places where it was needed

[1mi0]

• [*] My pull request is made against the dev branch.
• [*] I have ensured that the changed library can be built on your target system. I did not introduce any platform-specific code.
• [*] I have ensured that all methods and functions are fully documented using doxygen style comments.
• [*] I tested my commits, by adding a test case to the unit tests if needed
• [*] I have ensured that I did not break any existing API calls.
• [?] My code follows the coding style guide (if you are not sure, match the code style of existing files including indent style etc).
• [*] I have not built my pull request using AI, a static analysis tool or similar without any human oversight. Where I have generated this pull request using a tool, I have justified why this is needed.

[CLAassistant]

All committers have signed the CLA.

[braindigitalis]

thanks! please retarget this pr against the dev branch

[1mi0]

To answer all questions:
[[maybe_unused]] in our situation tells the compiler that we don't use the parameters inside of their functions. Not that we won't use them when we call the function or in other overloads | overrides of the function. In these specific 4 cases it just so happens that those arguments are not used inside of their lambda/function causing unused variable errors in my instance and warnings in other instances.