Automatically identifying caching target in IR level

Currently, there is no logic to identify data in the inside of loops to reuse them. Logic to identify what data inside loops get reused for efficient caching needs to be implemented. Right now, the IR identifies and creates loop operators with the help of LoopCompositeTransform, where a single LoopCompositeTransform exists in a loop. The optimal direction for this seems to be changing LoopCompositeTransform

Implementation would need:

LoopCompositeTransform needs to be augmented with the ability to inform the runtime of what data can be a candidate for caching