💡 Refactor Documentation from Readme to ReadTheDocs (#260)

This PR refactors the former Readme documentation to ReadTheDocs.

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Lukas Burgholzer <burgholzer@me.com>

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,45 @@
+name: 🐛 Bug report
+description: Something is not working correctly.
+title: "🐛 <title>"
+body:
+  - type: markdown
+    attributes:
+      value: >-
+        **Thank you for wanting to report a bug for this project!**
+
+        ⚠
+        Verify first that your issue is not [already reported on GitHub](https://github.com/cda-tum/mqt-bench/search?q=is%3Aissue&type=issues).
+
+        If you have general questions, please consider [starting a discussion](https://github.com/cda-tum/mqt-bench/discussions).
+  - type: textarea
+    attributes:
+      label: Environment information
+      description: >-
+        Please provide information about your environment. For example, OS, C++ compiler, mqt.core version etc.
+      placeholder: |
+        - OS:
+        - C++ compiler:
+        - mqt.core version:
+        - Additional environment information:
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Description
+      description: A clear and concise description of what the bug is.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected behavior
+      description: A clear and concise description of what you expected to happen.
+  - type: textarea
+    attributes:
+      label: How to Reproduce
+      description: Please provide steps to reproduce this bug.
+      placeholder: |
+        1. Get package from '...'
+        2. Then run '...'
+        3. An error occurs.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,32 @@
+name: ✨ Feature request
+description: Suggest an idea
+title: "✨ <title>"
+body:
+  - type: markdown
+    attributes:
+      value: >
+        **Thank you for wanting to suggest a feature for this project!**
+
+        ⚠
+        Verify first that your idea is not [already requested on GitHub](https://github.com/cda-tum/mqt-bench/search?q=is%3Aissue&type=issues).
+
+  - type: textarea
+    attributes:
+      label: What's the problem this feature will solve?
+      description: >-
+        What are you trying to do, that you are unable to achieve as it currently stands?
+      placeholder: >-
+        I'm trying to do X and I'm missing feature Y for this to be
+        easily achievable.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Describe the solution you'd like
+      description: >
+        Clear and concise description of what you want to happen.
+      placeholder: >-
+        When I do X, I want to achieve Y in a situation when Z.
+    validations:
+      required: true

.github/contributing.rst

@@ -0,0 +1,78 @@
+Contributing
+============
+
+Thank you for your interest in contributing to this project.
+We value contributions from people with all levels of experience.
+In particular if this is your first pull request not everything has to be perfect.
+We will guide you through the process.
+
+We use GitHub to `host code <https://github.com/cda-tum/mqt-bench>`_, to `track issues and feature requests <https://github.com/cda-tum/mqt-bench/issues>`_, as well as accept `pull requests <https://github.com/cda-tum/mqt-bench/pulls>`_.
+See https://docs.github.com/en/get-started/quickstart for a general introduction to working with GitHub and contributing to projects.
+
+Types of Contributions
+######################
+
+You can contribute in several ways:
+
+- 🐛 Report Bugs
+    Report bugs at https://github.com/cda-tum/mqt-bench/issues using the *🐛 Bug report* issue template. Please make sure to fill out all relevant information in the respective issue form.
+
+- 🐛 Fix Bugs
+    Look through the `GitHub Issues <https://github.com/cda-tum/mqt-bench/issues>`_ for bugs. Anything tagged with "bug" is open to whoever wants to try and fix it.
+
+- ✨ Propose New Features
+    Propose new features at https://github.com/cda-tum/mqt-bench/issues using the *✨ Feature request* issue template. Please make sure to fill out all relevant information in the respective issue form.
+
+- ✨ Implement New Features
+    Look through the `GitHub Issues <https://github.com/cda-tum/mqt-bench/issues>`_ for features. Anything tagged with "feature" is open to whoever wants to implement it. We highly appreciate external contributions to the project.
+
+- 📝 Write Documentation
+    MQT Bench could always use some more `documentation <https://mqt.readthedocs.io/projects/bench>`_, and we appreciate any help with that.
+
+🎉 Get Started
+##############
+
+Ready to contribute? Check out the :doc:`Development Guide <DevelopmentGuide>` to set up MQT Bench for local development and learn about the style guidelines and conventions used throughout the project.
+
+We value contributions from people with all levels of experience.
+In particular if this is your first PR not everything has to be perfect.
+We will guide you through the PR process.
+Nevertheless, please try to follow the guidelines below as well as you can to help make the PR process quick and smooth.
+
+Core Guidelines
+###############
+
+- `"Commit early and push often" <https://www.worklytics.co/blog/commit-early-push-often>`_.
+- Write meaningful commit messages (preferably using `gitmoji <https://gitmoji.dev>`_ to give additional context to your commits).
+- Focus on a single feature/bug at a time and only touch relevant files. Split multiple features into multiple contributions.
+- If you added a new feature, you should add tests that ensure it works as intended. Furthermore, the new feature should be documented appropriately.
+- If you fixed a bug, you should add tests that demonstrate that the bug has been fixed.
+- Document your code thoroughly and write readable code.
+- Keep your code clean. Remove any debug statements, left-over comments, or code unrelated to your contribution.
+- Run :code:`pre-commit run -a` to check your code for style and linting errors before committing.
+
+Pull Request Workflow
+#####################
+
+- Create PRs early. It is ok to create work-in-progress PRs. You may mark these as draft PRs on GitHub.
+- Describe your PR. Start with a descriptive title, reference any related issues by including the issue number in the PR description, and add a comprehensive description of the changes. We provide a PR template that you can (and should) follow to create a PR.
+- Whenever a PR is created or updated, several workflows on all supported platforms and versions of Python are executed. Make sure your PR passes *all* these continuous integration (CI) checks. Here are some tips for finding the cause of certain failures:
+  - If any of the :code:`Python Packaging/\*` checks fail, this indicates an error in the creation of the Python wheels and/or source distribution. Look through the respective logs on GitHub for any error or failure messages.
+  - If any of the :code:`Python/\*` checks fail, this indicates an error in the Python part of the code base. Look through the respective logs on GitHub for any error or failure messages.
+  - If any of the :code:`codecov/\*` checks fail, this means that your changes are not appropriately covered by tests or that the overall project coverage decreased too much. Ensure that you include tests for all your changes in the PR.
+  - If the :code:`docs/readthedocs.org:mqt-bench` check fails, the documentation could not be built properly. Inspect the corresponding log file for any errors.
+  - If the :code:`pre-commit.ci` check fails, some of the :code:`pre-commit` checks failed and could not be fixed automatically by the *pre-commit.ci* bot. Such failures are most likely related to the Python part of the code base. The individual log messages frequently provide helpful suggestions on how to fix the warnings.
+
+- Once your PR is ready, change it from a draft PR to a regular PR and request a review from one of the project maintainers.
+- If your PR gets a "Changes requested" review, you will need to address the feedback and update your PR by pushing to the same branch. You don't need to close the PR and open a new one. Respond to review comments on the PR (e.g., with "done 👍"). Be sure to re-request review once you have made changes after a code review so that maintainers know that the requests have been addressed.
+
+.. raw:: html
+
+    <hr>
+
+This document was inspired by and partially adapted from
+
+- https://matplotlib.org/stable/devel/coding_guide.html
+- https://opensource.creativecommons.org/contributing-code/pr-guidelines/
+- https://yeoman.io/contributing/pull-request.html
+- https://github.com/scikit-build/scikit-build

.github/support.rst

@@ -0,0 +1,12 @@
+Support
+=======
+
+If you are stuck with a problem using MQT Bench or have questions, please do get in touch at our `Issues <https://github.com/cda-tum/mqt-bench/issues>`_ or `Discussions <https://github.com/cda-tum/mqt-bench/discussions>`_. We'd love to help.
+
+You can save time by following this procedure when reporting a problem:
+
+- Do try to solve the problem on your own first. Make sure to consult the `Documentation <https://mqt.readthedocs.io/projects/bench>`_.
+- Search through past `Issues <https://github.com/cda-tum/mqt-bench/issues>`_ to see if someone else already had the same problem.
+- Before filing a bug report, try to create a minimal working example (MWE) that reproduces the problem. It's much easier to identify the cause for the problem if a handful of lines suffice to show that something isn't working.
+
+You can also always reach us at `quantum.cda@xcit.tum.de <mailto:quantum.cda@xcit.tum.de>`_.