Docs: refactor structure of documentation

[IceKhan13]

What is the expected enhancement?

Feedback:

• to dev focused
• have a structure as a story that users can follow along
• remove duplication
• focus on main features on main page

New proposed structure:
Main page:

• picture
• what is serverless and why do researcher needs it
• cover core concepts

General structure:

• quickstart
• setup
• running
• concepts
  • programming model
  • compute resources and resource allocation
• tutorials
  • VQE
  • distributed transpilation
• troubleshooting

Issues in epic:

• Docs: incorporate get_jobs into tutorials and getting started materials #450
• Docs: update client readme #332
• Docs: migrate all tutorials and guides that are not using programs to rst non-executable files #319
• docs/guides/06_shared_state.ipynb fails #489
• docs/guides/03_runtime_primitives_with_quantum_serverless.ipynb fails #488