check memory location of things tagged STATIC_MEMORY_LOCATION by default

[t-vi]

...in the prologue.
This could be tricky because it needs the real tensors, in particular if we try to move materializaton to later.

Implementation strategy could be

• add the data_ptr as an optional field to the TensorProxy
• include this in the check metadata

Note that pruning the checks would give the option to remove it, which is a good thing IMO.

[IvanYashchuk]

What's the intended usage of the STATIC_MEMORY_LOCATION tag? Is having data_ptr enough to check that something has static memory? Are strides and memory offset important here?

That's an interesting idea of adding data_ptr as an optional field to the TensorProxy. What should happen if any of the primitives creating TensorProxies sets this value?

Should Thunder have a different kind of TensorProxy for collecting information from the outside world (here converting torch.Tensor -> TensorProxy) and internal to Thunder functions intermediates that use TensorProxy?