Move Exp into libraries instead of intrinsics

Conceptual overview

Right now, Exp lives in the Microsoft.Quantum.Intrinsic namespace in part because of built-in decompositions for it in the native simulators. However, it is an advanced operation that does not map well to hardware intrinsics and requires advanced decomposition. Keeping it in the Intrinsic namespace is a little misleading, especially considering full support for it on hardware targets is challenging. We should deprecate the version in Microsoft.Quantum.Intrinsic in favor of a reasonable decomposition that lives in the libraries.

Child issues

• Deprecation of Exp in qsharp-runtime: Deprecate Exp in favor of libraries implementation qsharp-runtime#999
• Introduction of two-qubit rotations in qsharp-runtime: Add two-qubit rotation gates to Microsoft.Quantum.Intrinsic as fully supported APIs qsharp-runtime#1000

Proposal

New and modified functions, operations, and UDTs

Exp would be written in terms of decomposition of intrinsics and hosted in the libraries in an appropriate namespace. Exp in the Intrinsic namespace would be deprecated. The new decomposition could make use of explicit two-qubit rotation gates that would be introduced in the Intrinsic namespace (see child issues).

Open design questions and considerations

• Should there still be a way for the native simulator to override the decomposition in favor of it's built-in support or should it always use the common decomposition?
• Should the Exp use two qubit rotation or decompose all the way into single qubit rotation gates? If two-qubit rotation is added to Intrinsics (possible itself decomposed), does it matter?
• Should it be added to an exiting namespace or be the first member of some new namespace?