Adding prototype kata to test changes in magics

[Manvi-Agrawal]

This PR contains changes for testing the functionality of magics for the changes done in PR#620

The approach used in this Prototype kata is as per the following suggestion

The tests are failing on simulators on which they shouldn't pass are included in this PR as per suggestions here.

Note :

• Running dotnet test --filter Name~T11_PassOnToffoliSimulator reports a time ~100 ms, so hopefully we should be able to retain this test

TODO

• [ ] Clearup things : remove commented cells from the jupyter notebook
• [ ] Remove T11_PassOnToffoliSimulator from the exclusion after merging of https://github.com/microsoft/QuantumKatas/pull/620 and when alpha-builds are generated. Currently it wouldn't pass since CounterSimulator wont be able to manipulate 150 qubits.

[Manvi-Agrawal]

Hi @tcNickolas, I was wondering if I should break this PR into 2 parts for an easy review? First part will contain only README and *.qs files and other part will contain notebook frontend. Thoughts?

[tcNickolas]

We will be migrating the Katas to the new QDK that will use a different infrastructure (see https://devblogs.microsoft.com/qsharp/introducing-the-azure-quantum-development-kit-preview/ for the announcement), including a much faster simulator, so we won't continue to improve the existing infrastructure of Q# notebooks magics.

Thank you for your work on this, and apologies for not being able to incorporate it in our code earlier!

[Manvi-Agrawal]

Thanks @tcNickolas and @anjbur for your valuable guidance.

Looking forward to the new kata experience. Just had a look at https://quantum.microsoft.com/en-us/experience/quantum-katas, and the experience looks way more polished :-)