[clang] Thread Safety Analysis: Drop call-based alias invalidation (PR #187691)

[Marco Elver via cfe-commits]

melver wrote:

> I had to revert because it causes Linux kernel build errors (false positives), so I need to take another look.

I think we need to retain a very narrow heuristic, see: https://github.com/llvm/llvm-project/pull/190154

In particular, I didn't like that we effectively undid what testPointerAliasEscapeMultiple() was testing (avoid false negatives for this case, which @ziqingluo-90 fixed earlier). And I found real cases in the Linux kernel where there's some reallocation of an object going on that I *do* want to catch (or suppress explicitly).

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