[llvm] [NFC][Scalarizer][TargetTransformInfo] Add `isVectorIntrinsicWithOverloadTypeAtArg` api (PR #114849)

[Chris B via llvm-commits]

llvm-beanz wrote:

> Does it make sense to make a few issues for this and let this pr go in as is? I started this pattern with some of the other isVectorIntrinsic functions so feels like the cleanup should cover all the functions.

It seems clear to me that we should file issues to fix the other cases, but I don't see why we would merge this one, then just have to clean it up. This is an NFC change, having the NFC refactoring end up in the correct end state seems better to me.


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