bugprone-use-after-move should catch std::optional::has_value

[higher-performance]

Per #114255 (comment), std::optional::has_value should probably be considered bug-prone after a move, since it implies the use of std::optional::value afterward, which is moved-from.

[llvmbot]

@llvm/issue-subscribers-clang-tidy

Author: None (higher-performance)

Per https://github.com//pull/114255#discussion_r1826547993, `std::optional::has_value` should probably be considered bug-prone after a move, since it implies the use of `std::optional::value` afterward, which is moved-from.

[chrchr-github]

Looks like there already is a warning for the given example: https://godbolt.org/z/j55Tc9bxr

[higher-performance]

I think I might be confused here -- or maybe this issue will arise once the PR is merged? Sorry for the noise, we can come back to this once the PR is done.