type load exceptions from the bound msbuild libraries can escape being caught and handled by the failure loop

[baronfel]

Describe the bug

If there's a mismatch in the msbuild dlls, then a typeloadexception will escape the error handling present in the library.

The first time the libraries are loaded are on calls to this function. This call happens here. Therefore, we should catch exceptions here and bubble that up as a Result.Error so that the error can be reported by the notification event handler as we expect, instead of being uncaught and never notifying callers.

[TheAngryByrd]

@baronfel think this is still an issue?