Fix loop rotate when header has instructions producing ownership results

[meg-gupta]

LoopRotate currently should avoid moving instructions that produce ownership results to the loop header. Such instructions may have uses with the loop that cannot be moved to the loop header causing over consume ownership verifier errors.

rdar://145086395

[meg-gupta]

Extracted bug fix from #79198

[meg-gupta]

@swift-ci test

[meg-gupta]

@swift-ci test

[meg-gupta]

@swift-ci test Linux platform

[meg-gupta]

@swift-ci test Linux platform

[meg-gupta]

@swift-ci test Linux platform

[eeckstein]

@swift-ci apple silicon benchmark

[eeckstein]

lgtm!
Let's make sure nothing bad happens to the benchmarks before merging.

[meg-gupta]

------- Performance (arm64): -O -------

REGRESSION                      OLD       NEW     DELTA    RATIO    
Set.subtracting.Seq.Empty.Box   58.542    81.04   +38.4%   **0.72x (?)**
COWTree                         864.615   952.0   +10.1%   **0.91x (?)**

------- Code size: -O -------

------- Performance (arm64): -Osize -------

REGRESSION                  OLD       NEW      DELTA    RATIO    
ArrayAppendGenericStructs   881.538   1135.0   +28.8%   **0.78x (?)**

IMPROVEMENT                 OLD       NEW      DELTA    RATIO    
ArrayOfGenericRef           655.0     596.25   -9.0%    **1.10x (?)**

------- Code size: -Osize -------

------- Performance (arm64): -Onone -------

IMPROVEMENT                 OLD        NEW       DELTA    RATIO    
ArrayAppendGenericStructs   1187.778   740.625   -37.6%   **1.60x (?)**

------- Code size: -swiftlibs -------

I don't see any meaningful change here.

Note that we are not avoiding LoopRotate in cases where the header has instructions producing ownership results. We are only avoiding hoisting them when they have invariant operands, LoopRotate can still duplicate such instructions provided it doesn't exceed the threshold.

Merging to fix issue.