[release/10.0] Fixup some Vector<T> function lookups to use the right name/type

[github-actions]

Backport of #119068 to release/10.0 (RC2)

/cc @tannergooding @jeffhandley

Customer Impact

• Customer reported
• Found internally

Developers using Vector comparison APIs would see incorrect behavior for some overloads; while those using SquareRoot would see reduced performance.

Regression

• Yes
• No

The regressions were introduced as part of the several refactorings that removed the independent simdashwintrinsic support and changed it to reuse the hwintrinsic paths.

The general issue is that the System.Numerics vector API surface differs slightly from the modern System.Runtime.Intrinsics API surface. Namely it exposes some "legacy" overloads of the comparison APIs that return Vector<int> for comparisons involving Vector<float> and which uses a different name for a few APIs. While most of these special edge cases were handled as part of removing the simdashwintrinsic support, a couple were missed.

Testing

An explicit test covering the customer reported regression was added. Manual validation of the related scenarios and codegen was done.

Risk

Low. This is simply adding the long-existing flags to the table relevant table entries to ensure they go down the right code paths. There isn't really any "net new" code here which could introduce risk.

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

[lewing]

@artl93 since release/10.0 is m2 I assume your approval means this is servicing approved now?