How should lazy actx.compile interact with memoization (on the output end)?

This is a longer-shot companion issue to https://github.com/inducer/pytato/issues/164 (and https://github.com/inducer/arraycontext/issues/99).

Suppose an `actx.compile`d function evaluates something that's memoized (for the sake of argument, imagine a temperature in mirgecom). After the compiled evaluation concludes, the memoization of dependent data becomes unavailable, since we're now working on a different array (/array container) instance. It'd be nice if that weren't the case.

(This isn't immensely relevant for mirgecom, since the output of the `compile`d function will typically be fed into a time integrator, which would invalidate any memoized temperature anyhow.)

cc @kaushikcfd

先閱讀配套的 issue inducer/pytato#164 和 inducer/arraycontext#99，然後追蹤 actx.compile 在被評估函式使用 memoized data 的情況下的行為。比較編譯評估前後的 array 或 array-container 實例。如果這種行為可行，則在編譯後相依資料的記憶化仍然可用，即視為完成。

由索引模型根據 Issue 內容生成。