Preserve the IRestrictedErrorInfo after reading it.

[tristanlabelle]

For crash reporting purposes, it is useful to keep the error state, so a crash handler can call GetErrorInfo.

[stevenbrix]

as-is, this will only provide information for RoOriginateError, which doesn't account for all possible errors. we should store the error info or see if RoGetMatchingRestrictedErrorInfo does the trick

[tristanlabelle]

Abandoning since we found a better solution in our scenario (detouring swift_unexpectedError).

The WinRT error handling model is that the projection should retrieve and clear the IRestrictedErrorInfo, and then propagate that using the language's error mechanism as necessary. RoOriginateError is meant only to attach additional information to the HRESULT as it transitions out of the WinRT component and into the projection, not as a log of the last recorded error.