RequireAnalysis<GlobalsAA> doesn't actually recompute GlobalsAA.
GlobalsAA isn't invalidated (unless specifically invalidated) because
it's self-updating via ValueHandles, but can be imprecise during the
self-updates.
Rather than invalidating GlobalsAA, which would invalidate AAManager and
any analyses that use AAManager, create a new pass that recomputes
GlobalsAA.
Fixes #53131.
Is there a drawback to just doing MPM.addPass(InvalidateAnalysisPass<GlobalsAA>()); before re-requiring GlobalsAA? At least for the test case, it looks like this is sufficient.