Fix remote pipeline shader reflection retrieval

[samtou-arm]

Serialise remote ShaderReflection pointers as opaque uint64 values and resolve them through a proxy-local RPC. Cache the resulting reflections by pointer value, avoiding reconstruction of backend-specific GetShader parameters and correctly handling shader replacements across APIs.

This PR aims to address the maintainer's comment on this upstream PR: baldurk#3879

Basically, my understanding of the approach is:

• Whenever we save the Pipeline State, just before serialising, we add the pointer value in an array (as a uint64_t).
• We create a duplicate map keyed by that value that we will use for cache purposes.
• When it comes to retrieve the shader, we query that new reflection cache and if we don't find the value that we stored in our vector of shader stages, we go and query the remote to serialise the entire reflection shader to create a local copy on the host, stored in the reflection cache.

Point of attention:

• Not 100% sure of the transfer to the DummyDriver and the Clearing in the destructor
• Not sure about the D3D11 special case handling for the input assembly stage

It's all tested on Windows + Linux (D3D11, D3D12, Vulkan and OpenGL) in both ways (Windows remote server then Linux remote server).