[llvm] [ValueTracking] Make the MaxAnalysisRecursionDepth overridable (PR #137721)

[Jeffrey Byrnes via llvm-commits]

jrbyrnes wrote:

Reworked the API such that the exhaustive analysis is now a separate util rather than cl option. I've also used a tracking mechanism to signal infinite loops and exit. This is done via a DenseMap of instructions, which has some overhead, however, the underlying principle of the exhaustive analysis is to pay more computation for increased chances of optimization.

I've included the usecase + test as well.

I'm still working on testing, but I am sort of settled on the implementation and am curious if there are any concerns.

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