Prevent managed messaging initialization if profiler is not loaded

[jander-msft]

Summary

When parameter capturing is not enabled and no other feature is enabled that requires the profiler, the startup hook will throw a DllNotFoundException exception, which appears in the /exceptions history backlog. This happens because the startup hook is attempting to initialize the managed messaging dispatcher, which requires the profiler to have been loaded.

Overview of changes:

• Add an additional check of whether the profiler is loaded before attempting to initialize the dispatcher.
• Add tests to verify the availability of the dispatcher based on the existence of the profiler.

Release Notes Entry