🗃 Add default issue template for new tickets

This commit imports the Community Ops Team default issue template. It
leverages some of the new features we have on Forgejo with the front-
matter configuration and issue forms, such as providing default issue
labels on new issues.

A config file is also provided, to give some other link options that
someone will see when opening a new issue, such as our Matrix room and
the Fedora Discussion tag for the Council.

Hopefully, this gives us a framework to have more useful, structured
data for new tickets that the Fedora Council receives. It is sort of
forced too, as all new issues cannot use a blank issue; they must use
the default template.

Signed-off-by: Justin Wheeler <jwheel@redhat.com>

.forgejo/issue_template/config.yml

@@ -0,0 +1,12 @@
+---
+# Disable blank issues to force template usage
+blank_issues_enabled: false
+
+# Provide alternative support channels for the Fedora Council
+contact_links:
+  - name: Fedora Council Matrix Room
+    url: https://matrix.to/#/#council:fedoraproject.org
+    about: Join our Matrix room to ask questions before opening a Fedora governance docs ticket.
+  - name: council tag on Fedora Discussion
+    url: https://discussion.fedoraproject.org/tags/c/project/7/council/
+    about: Read asynchronous updates and discussions from the Fedora Council.

.forgejo/issue_template/default.yml

@@ -0,0 +1,60 @@
+---
+name: Fedora Governance Docs Request
+about: Use this template for any ticket that does not fit within another template.
+labels:
+  - '?/needs triage'
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Welcome to the Fedora Governance Documentation general request form!
+        This form is designed to help us identify bugs and improvements to the existing Fedora Governance Documentation sites, e.g., `/project/`, `/council/`, `/engineering/`, and `/mindshare/`. Use this issue template to file a ticket.
+
+  - type: checkboxes
+    id: antora-component
+    attributes:
+      label: Antora Components
+      description: Check the boxes to indicate which Antora components your ticket is related to. Select all that apply.
+      options:
+        - label: "**Project** – docs.fp.o/en-US/project/"
+        - label: "**Council** – docs.fp.o/en-US/council/"
+        - label: "**Engineering** – docs.fp.o/en-US/engineering/"
+        - label: "**Mindshare** – docs.fp.o/en-US/mindshare/"
+        - label: "**None of the above** – I am reporting something else"
+    validations:
+      required: true
+
+  - type: input
+    id: summary
+    attributes:
+      label: Summary
+      description: In one sentence, describe your suggestion, idea, or task.
+      placeholder: e.g., Fix outdated Fedora Council membership on the `members.adoc` page.
+    validations:
+      required: true
+
+  - type: textarea
+    id: background
+    attributes:
+      label: Background
+      description: Give context or background needed to understand your suggestion, idea, or task. Preferably between two to five sentences. This helps us understand the "why".
+    validations:
+      required: true
+
+  - type: textarea
+    id: details
+    attributes:
+      label: Details
+      description: Describe the necessary steps to satisfactorily complete your suggestion, idea, or task. It is preferred to write this as a step-by-step list. However, you can also describe the work needed in two to five sentences. This helps us understand the "how" of your request.
+    validations:
+      required: true
+
+- type: input
+    id: outcome
+    attributes:
+      label: Summary
+      description: In one sentence, describe the expected outcome or impact of completing your suggestion, idea, or task.
+      placeholder: e.g., The Fedora community can quickly discover who is a current member of Fedora Council.
+    validations:
+      required: true