documentation update

[scarrazza]

This PR updates the documentation for the following points:

• applications are now sorted by topic and algorithms.
• installation instructions include qibojit and qiboicarusq.

[codecov]

Codecov Report

Merging #435 (f39a6e9) into warnings (d88a3b3) will not change coverage.
The diff coverage is n/a.

❗ Current head f39a6e9 differs from pull request most recent head 6ff50dc. Consider uploading reports for the commit 6ff50dc to get more accurate results

@@            Coverage Diff             @@
##           warnings      #435   +/-   ##
==========================================
  Coverage    100.00%   100.00%           
==========================================
  Files            83        83           
  Lines         11867     11867           
==========================================
  Hits          11867     11867           

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d88a3b3...6ff50dc. Read the comment docs.

[stavros11]

Thanks for the update, looks good to me. The only thing is that this documentation assumes that qibotf is the default backend and qibojit as experiment that should be enabled using qibo.set_backend. This will not be true after we merge #436 as qibojit will become the default backend. Shall we update the docs for this?

[stavros11]

qibojit does not support multi-GPU currently so we should probably remove the multi-GPU from this line and put it back once we enable this feature.

[scarrazza]

@stavros11 thanks, I have fixed this issue and resorted the backend priority.

[igres26]

It also looks good to me.

However I would like to make one quick request as we are working on the documentation here already.

When one searches in the documentation for "Adiabatic evolution" or "Quantum Fourier Transform" the first thing that pops up is the benchmarks, but they are not labelled as benchmarks so it's easy to get confused and enter in the wrong documentation part. I would add "benchmark" to the parts of the documentation that are benchmarks.

[scarrazza]

@igres26 thanks for pointing this out. I have introduced some changes that should help clarifying that is benchmark from what is not. Most likely we should remove the benchmark section soon in the future, given that the code is evolving quickly.