[clang-tools-extra] [clang-tidy] Extend `bugprone-use-after-move` to allow custom invalidation functions (PR #170346)

[Baranov Victor via cfe-commits]

vbvictor wrote:

> I've seen reports from users who were confused about a bugprone-use-after-move diagnostic they were getting because "there is no move in my code".

Could you give some examples that are confusing to read.

By default the check does not use any custom invalidation functions, so the must have been specified explicitly or..? 

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