[clang-tools-extra] Extend bugprone-use-after-move check to handle std::optional::reset() and std::any::reset() (PR #114255)

[via cfe-commits]

================
@@ -196,9 +196,10 @@ Any occurrence of the moved variable that is not a reinitialization (see below)
 is considered to be a use.
 
 An exception to this are objects of type ``std::unique_ptr``,
-``std::shared_ptr`` and ``std::weak_ptr``, which have defined move behavior
-(objects of these classes are guaranteed to be empty after they have been moved
-from). Therefore, an object of these classes will only be considered to be used
+``std::shared_ptr``, ``std::weak_ptr``, ``std::optional``, and ``std::any``,
+which have defined move behavior (objects of these classes are guaranteed to be
+empty after they have been moved from).
----------------
higher-performance wrote:

Actually, reading it again, I think I should just take out the explanation---this section is saying something slightly different. The explanation is already covered by the "Reinitialization" section underneath.

Please see update.

https://github.com/llvm/llvm-project/pull/114255