Give more meaningful error in UiaOperationAbstraction when MalformedBytecode is returned from the operation

[beweedon]

MalformedBytecode can occur when:

• The size of the bytecode is above the maximum size
• The bytecode version isn't supported by the provider-side UIA
• An unsupported opcode is used
• An opcode is used improperly (e.g. it's at the end of the bytecode stream even though it should take arguments)
• Generally any part of the initial remote operation state (e.g. bytecode, imports, requested results, etc.) fails to be read on the remote side

Currently UiaOperationAbstraction throws E_FAIL from Resolve when MalformedBytecode is encountered. It might be good to throw a more informative error, or provide a mechanism to detect when the error is due to MalformedBytecode.

@zhayuli