[vLLM IR] Port RoPE ops to IR

[ProExpertProg]

There are many flavors of rope, but some of them only contain a native implementation; those do not need to be ported. Additionally, the sin_cos_cache initialization logic should remain in the layer. At the very least, the following should be ported:

• RotaryEmbedding
• DeepseekScalingRotaryEmbedding

However, we should carefully inspect semantics if any of the ops can be consolidated, especially using simple bool params. This will help us reduce the maintenance burden and increase the coverage for rope+cache related fusions.

Final challenge for rope will be the inplace semantics, as the _C implementation is fully inplace, and the arguments are views, which will complicate the aliasing analysis for the clone elimination after the lowering pass (see #36823)

[wxsIcey]

I'd be happy to work on the Rope. You can assgin it to me.