Expose the underlying bytecode built by the Builder library

[mlalic]

From Adam Hodson:

If I put together a remote operation using the winRT builder api, is there a way to get back the generated byte code for the series of calls strung together? The presented slide on diagnostics functionality assumes you're using byte code for the error location so wouldn't be that helpful if you used the builder api?

---

Yes, exposing the actual bytecode generated by the builder out to the client would certainly be useful. We should add this.

We could perhaps have both a "current bytecode" exposed off of the AutomationRemoteOperation itself (the bytecode that has been built up thus far), as well as an "executed bytecode" property on the ResultSet (the bytecode that was ultimately sent for execution).