Currently we populate the prism MTLCommandQueue details in common class QuantumRenderer in metal repo and then use it on Glass side.

In MTLPipeline we have to make sure that we create devicedetails object when Pipeline is initialised from Quantum Renderer and then populate the commandQueue into the devidedetails when we call for creation of resource factory comes from QuantumRenderer. This makes sure that glass has commandQueue details and same approach is followed in ES2 pipeline.

By doing this we can remove common change in QuantumRenderer to setDeviceDetails.