Improve usability of Program Cache handling in Device Operations

[ayerofieiev-tt]

Developers consistently hit issues with program cache.

• It is not clear that Device Operation class must provide a hash for {program + compile time args}
• It is not clear that same Program might get called multiple times if returned hash is the same
• It is not clear that a proper update function must be provided so that a program could be called with different runtime arguments
• There is no established testing pattern to check variability in operation arguments and behavior with and without program cache enabled

Keep in mind, there are 2 ways to define a Device Operation today (see topk vs dropout)

---

Link known failures here:

• #17972 and #17975 Fixing PCC and Program Cache issues in Repeat and Expand #18002