chore: Move Readmes content to Docs, refresh index and adjust Docusaurus configurations

Signed-off-by: Gabryel Nóbrega <gabryelster@gmail.com>

Author: see7e

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,39 +1,39 @@
----
-name: "\U0001F41E Bug report"
-about: Report a bug or known issue
-title: ''
-labels: 'type: bug'
-assignees: ''
-
----
-
-Prior to submitting an issue, check to see if one has already been created. If there is currently an open issue, add a thumbs-up emoji to identify that it is also affecting you.
-
-### Your Environment
-
-- **Version:**
-- **Affected Scope:** docker, docussaurus, internationalization, docs, docs-spanish, docs-portuguese.
-- **Deployment Environment:** e.g. docker, baremetal, vs-code, docker compose, virtualbox.
-
-### Describe the Issue
-
-A clear and concise description of what the bug is.
-
-#### To Reproduce
-
-1. Go to '...'
-2. Click on '....'
-3. Scroll down to '....'
-4. See error
-
-#### Expected behavior
-
-A clear and concise description of what you expected to happen.
-
-#### Screenshots
-
-If applicable, add screenshots to help explain your problem.
-
-#### Additional context
-
-Add any other context about the problem here (e.g. logs).
+---
+name: "\U0001F41E Bug report"
+about: Report a bug or known issue
+title: ''
+labels: 'type: bug'
+assignees: ''
+
+---
+
+Prior to submitting an issue, check to see if one has already been created. If there is currently an open issue, add a thumbs-up emoji to identify that it is also affecting you.
+
+### Your Environment
+
+- **Version:**
+- **Affected Scope:** docker, docussaurus, internationalization, docs, docs-spanish, docs-portuguese.
+- **Deployment Environment:** e.g. docker, baremetal, vs-code, docker compose, virtualbox.
+
+### Describe the Issue
+
+A clear and concise description of what the bug is.
+
+#### To Reproduce
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+#### Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+#### Screenshots
+
+If applicable, add screenshots to help explain your problem.
+
+#### Additional context
+
+Add any other context about the problem here (e.g. logs).

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,36 +1,36 @@
----
-name: "\U0001F680 Feedback form"
-about: Describe a problem, suggest a new idea or functionality for the project
-title: ''
-labels: 'type: feature'
-assignees: ''
-
----
-
-### Your Environment (If applicable)
-
-- **Version:**
-- **Affected Scope:** docker, docussaurus, internationalization, docs, docs-spanish, docs-portuguese.
-- **Deployment Environment:** e.g. docker, baremetal, vs-code, docker compose, virtualbox.
-
-### Describe the problem
-
-#### Description
-
-A clear and concise description of what the problem is, under which scenarios or how frequent it happen
-
-#### Additional context
-
-Add any other context or screenshots about the problem here. You can also provide links to relevant resources.
-
-### Describe your idea (optional)
-
-A clear and concise description of any alternative solutions or features you've considered.
-
-#### Additional context
-
-Add any other context or screenshots about your solution.
-
-#### Desired timelines
-
-Share any information about timeline expectations.
+---
+name: "\U0001F680 Feedback form"
+about: Describe a problem, suggest a new idea or functionality for the project
+title: ''
+labels: 'type: feature'
+assignees: ''
+
+---
+
+### Your Environment (If applicable)
+
+- **Version:**
+- **Affected Scope:** docker, docussaurus, internationalization, docs, docs-spanish, docs-portuguese.
+- **Deployment Environment:** e.g. docker, baremetal, vs-code, docker compose, virtualbox.
+
+### Describe the problem
+
+#### Description
+
+A clear and concise description of what the problem is, under which scenarios or how frequent it happen
+
+#### Additional context
+
+Add any other context or screenshots about the problem here. You can also provide links to relevant resources.
+
+### Describe your idea (optional)
+
+A clear and concise description of any alternative solutions or features you've considered.
+
+#### Additional context
+
+Add any other context or screenshots about your solution.
+
+#### Desired timelines
+
+Share any information about timeline expectations.

.github/ISSUE_TEMPLATE/proposal.md

@@ -1,36 +1,36 @@
----
-name: "\U0001F4A1 Proposal"
-about: Propose a change to the Magma project
-title: ''
-labels: 'type: proposal'
-assignees: ''
-
----
-
-<!--
-
-Please start by reading the proposals process overview: https://docs.magmacore.org/docs/contributing/contribute_proposals
-
-The key difference between a "feature request" and a "proposal" is the latter propose an actionable solution.
-
-Proposal contents are not limited to particular topics, though the following are typical
-
-- Process improvements
-- Design changes
-- Shift in project goals
-
-For non-trivial proposals, consider following this standard pitch template, reproduced below in-part: https://github.com/kbariotis/templates/blob/master/templates/PITCH/TEMPLATE.md
-
--->
-
-### Problem
-
-The raw idea, a use case, or something that motivates acting on this proposal
-
-### Solution
-
-The core elements of the solution, presented concisely, targeting an audience with high-breadth but low-depth understanding of Magma
-
-### Non-goals
-
-Anything specifically excluded from the concept
+---
+name: "\U0001F4A1 Proposal"
+about: Propose a change to the Magma project
+title: ''
+labels: 'type: proposal'
+assignees: ''
+
+---
+
+<!--
+
+Please start by reading the proposals process overview: https://docs.magmacore.org/docs/contributing/contribute_proposals
+
+The key difference between a "feature request" and a "proposal" is the latter propose an actionable solution.
+
+Proposal contents are not limited to particular topics, though the following are typical
+
+- Process improvements
+- Design changes
+- Shift in project goals
+
+For non-trivial proposals, consider following this standard pitch template, reproduced below in-part: https://github.com/kbariotis/templates/blob/master/templates/PITCH/TEMPLATE.md
+
+-->
+
+### Problem
+
+The raw idea, a use case, or something that motivates acting on this proposal
+
+### Solution
+
+The core elements of the solution, presented concisely, targeting an audience with high-breadth but low-depth understanding of Magma
+
+### Non-goals
+
+Anything specifically excluded from the concept

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,35 +1,35 @@
-<!--
-    Tag your PR title with the components that it touches along with
-    the type of change
-    E.g. "fix(docussaurus): spanish content configuration" or "feat(docker) ..."
--->
-
-## Summary
-
-<!-- Enumerate changes you made and why you made them -->
-
-## Test Plan
-
-<!--
-    How did you test your change? How do you know it works?
-    Add supporting screenshots, terminal pastes, etc. as necessary
--->
-
-## Additional Information
-
-- [ ] This change is backwards-breaking
-
-<!--
-    If this is a backwards-breaking change, document the upgrade instructions.
-    Is any action necessary to upgrade an existing instance other than restarting?
-    All upgrade instructions for backwards-breaking changes will be aggregated
-    in the next release's changelog so this is very important to fill out.
--->
-
-## Security Considerations
-
-<!--
-    Comment on potential security impact. Could the change create or 
-    eliminate weaknesses? STRIDE, OWASP Top 10, or RFC 3552 may help.
--->
-
+<!--
+    Tag your PR title with the components that it touches along with
+    the type of change
+    E.g. "fix(docussaurus): spanish content configuration" or "feat(docker) ..."
+-->
+
+## Summary
+
+<!-- Enumerate changes you made and why you made them -->
+
+## Test Plan
+
+<!--
+    How did you test your change? How do you know it works?
+    Add supporting screenshots, terminal pastes, etc. as necessary
+-->
+
+## Additional Information
+
+- [ ] This change is backwards-breaking
+
+<!--
+    If this is a backwards-breaking change, document the upgrade instructions.
+    Is any action necessary to upgrade an existing instance other than restarting?
+    All upgrade instructions for backwards-breaking changes will be aggregated
+    in the next release's changelog so this is very important to fill out.
+-->
+
+## Security Considerations
+
+<!--
+    Comment on potential security impact. Could the change create or 
+    eliminate weaknesses? STRIDE, OWASP Top 10, or RFC 3552 may help.
+-->
+