Consider compiling QIR Runtime into a pair - dynamic and static lib.

[kuzminrobin]

The code crossing the dynamic library boundary (ABI boundary) can bump into a number of issues. At least the C++ code.
The .ll code generated from the users' .qs files needs from QIR Runtime the @__quantum__rt__* and @__quantum__qis__* entry points only.
The rest of the APIs exposed by the QIR Runtime DLL, is needed by the Tests and Samples only.
To minimize the probability of the issues

1. Consider merging the following DLLs into a single DLL:

• Microsoft.Quantum.Qir.Runtime.dll
• Microsoft.Quantum.Qir.QSharp.Foundation.dll
• Microsoft.Quantum.Qir.QSharp.Core.dll

2. Consider splitting the QIR Runtime into:

• DLL exposing the @__quantum__rt__* and @__quantum__qis__* entry points only, with plain C interface (extern "C");
• Static Lib exposing the C++ APIs for Tests, Samples, etc. (the point is that the whole C++ interface is exposed as a static lib, rather than dynamic).

See related #631.

[kuzminrobin]

Closing in favor of this #711