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

[via cfe-commits]

martinboehme 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".

With this added functionality, the name of the check is now misleading. One solution would be to rename the check, but I think the better solution would be to split the new functionality out into a separate check.

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