[polly] [Polly] Fix invariant load hoisting when ancestor SAI is written in scop (PR #204800)

[Eli Friedman via llvm-commits]

efriedma-quic wrote:

> Potentially, we may need the aliasing tracker instead of finding a matching SAI.

My understanding is that if you have an invariant load and a store with different SAIs, we emit a runtime aliasing check.  The problem here is that the load and the store have the same SAI, so that infrastructure doesn't kick in.

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