Change issue templates to yaml forms

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,72 @@
+# SPDX-FileCopyrightText: Christopher Hock and the Nazara Team <[email protected]>
+# SPDX-License-Identifier: LGPL-3.0-only
+---
+name: Bug Report
+description: Found a bug? Let us know!
+title: "[BUG]"
+labels: ["bug", "pending"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        **NOTE**: Please only use this form to report _reproducible bugs_ in Nazara.
+        If you have any questions or are looking for assistance,
+        please refer to our [discussion section](https://github.com/orgs/The-Nazara-Project/discussions).
+  - type: input
+    attributes:
+      label: Nazara Version
+      description: >
+        Which version of Nazara does this bug affect?
+      placeholder: master
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: NetBox Version
+      description: >
+        Which version of NetBox are you running?
+      placeholder: v4.0.0
+  - type: dropdown
+    attributes:
+      label: NetBox Deployment Type
+      description: How are you running NetBox?
+      multiple: false
+      options:
+        - NetBox Cloud
+        - NetBox Enterprise
+        - Self-Hosted
+        - Docker
+  - type: dropdown
+    attributes:
+      label: Affected Module
+      description: >
+        Which module or area of Nazara does this affect?
+      multiple: true
+      options:
+        - Data Collection
+        - API Connection
+        - Configuration
+        - Dependencies
+        - Performance
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Bug Description
+      description: >
+        Please describe in detail what issue you face.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected Behaviour
+      description: >
+        Please describe what you exepected to happen.
+  - type: textarea
+    attributes:
+      label: Steps to Reproduce
+      description: >
+        Please describe what steps we need to take to reproduce this issue.
+        Please also include any relevant details about your environment (Host system, NetBox Version, etc.)
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/deprecation.yaml

@@ -0,0 +1,27 @@
+# SPDX-FileCopyrightText: Christopher Hock and the Nazara Team <[email protected]>
+# SPDX-LicenseIdentifier: GPL-3.0-only
+---
+name: Deprecation
+description: Suggest removing a feature or functionality from Nazara.
+labels: ["pending", "deprecation"]
+body:
+  - type: textarea
+    attributes:
+      label: Proposed Changes
+      description: >
+        Describe in detail what changes you ahve in mind.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Justification
+      description: >
+        Why do you want this change?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Impact
+      description: List all areas of Nazara, which will be impacted by this change.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/documentation_change.yaml

@@ -0,0 +1,42 @@
+# SPDX-FileCopyrightText: Christopher Hock and the Nazara Team <[email protected]>
+# SPDX-LicenseIdentifier: GPL-3.0-only
+---
+name: Documentation Change
+description: Suggest a change in Nazara's documentation
+labels: ["documentation", "pending"]
+body:
+  - type: dropdown
+    attributes:
+      label: Type of Change
+      description: What kind of change are you proposing?
+      multiple: false
+      options:
+        - Addition
+        - Correction
+        - Deprecation
+        - Maintenance (formatting, typos, grammar, etc.)
+    validations:
+      required: true
+  - type: dropdown
+    attributes:
+      label: Section
+      description: What section do you want to change?
+      multiple: false
+      options:
+        - Installation/Update
+        - Usage
+        - Configuration
+        - API Connection
+        - Code documentation
+        - Contribution Guide
+        - Security Policy
+        - License
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Proposed Change
+      description: Describe your desired change.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,58 @@
+# SPDX-FileCopryightText: Christopher Hock and the Nazara Team <[email protected]>
+# SPDX-License-Identifier: GPL-3.0-only
+---
+name: Feature Request
+description: Propose a new functionality or feature
+title: "[FR]"
+labels: ["proposal", "pending"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        **NOTE**: Please only use this form for submitting _well-formed_ proposals
+        to extend or enhance Nazara in some form. If you are trying to solve a problem,
+        or need help bringing your idea inot an actionable form, please use our [discussion section](https://github.com/orgs/The-Nazara-Project/discussions).
+  - type: input
+    attributes:
+      label: Nazara Version
+      description: What version of Nazara are you working with?
+      placeholder: master
+    validations:
+      required: true
+  - type: dropdown
+    attributes:
+      label: Feature Type
+      multiple: false
+      options:
+        - New Core Feature
+        - Change of Behaviour
+        - Performance Enhancement
+        - Maintenance Enhancement
+        - Usability Enhancement
+        - Other
+    validations:
+      required: true
+  - type: dropdown
+    attributes:
+      label: Affected Module
+      description: Which module of Nazara will be affected?
+      multiple: true
+      options:
+        - API Connection
+        - Automation Integration
+        - Configurations
+        - CLI Frontend
+        - Data Collection
+        - Payload Translation
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Proposal
+      description: >
+        Describe your idea in detail. Include any specific requirements
+        for your plan to work as well as the supposed benefit your feature will bring.
+        Also include an rough actionplan - if possible.
+        Feature requests with unclear or missing action plan may take longer to process.
+    validations:
+      required: true