Unknown compiler options for clang shouldn't be show-stoppers

[AndyZe]

Description

This is a workaround for a CI error that has been cropping up once in awhile recently:

Error while processing /home/runner/work/moveit2/moveit2/.work/target_ws/src/moveit2/moveit_ros/moveit_servo/src/utils/common.cpp.
error: unknown warning option '-Wno-maybe-uninitialized'; did you mean '-Wno-uninitialized'? [clang-diagnostic-unknown-warning-option]

From https://github.com/moveit/moveit2/actions/runs/10335417126/job/28609933300 for one example

I don't think there's actually a potentially uninitialized variable there, at least not a new one in this PR. I think what happened is, clang-tidy was cached previously for this cpp file. That PR happened to touch that cpp file, which caused clang-tidy to re-run for it. And something about clang-tidy has changed since the last time it ran.

[sea-bass]

I additionally searched for this issue and found this relevant post: https://stackoverflow.com/a/41673702

So this change makes sense to me, but would be nice for someone with more software chops than me to give it the final approval.

[rhaschke]

Maybe add a comment to remove that option in the future if clang-tidy is fixed.