feat: enhance issue templates with additional fields for better reporting

Author: TheMeinerLP

.github/ISSUE_TEMPLATE/behavior-bug-or-plugin-incompatibility.yml

@@ -1,36 +1,43 @@
 name: Behavior Bug or Plugin Incompatibility
 description: Report issues with plugin incompatibility or other behavior related issues.
 labels: [ "status: needs triage", "type: bug" ]
+projects: ["OneLiteFeatherNET/6"]
+assignees: ["OneLiteFeatherNET/antiredstoneclock-remastered-triage"]
 body:
   - type: textarea
+    id: server-logs
     attributes:
       label: Server Logs
       description: |
         Upload your server log from `logs/latest.log` here
     validations:
       required: true
   - type: textarea
+    id: expected-behavior
     attributes:
       label: Expected behavior
       description: What you expected to see.
     validations:
       required: true
 
   - type: textarea
+    id: actual-behavior
     attributes:
       label: Actual behavior
       description: What you actually saw.
     validations:
       required: true
 
   - type: textarea
+    config: steps-to-reproduce
     attributes:
       label: Steps to reproduce
       description: This may include a build schematic, a video, or detailed instructions to help reconstruct the issue.
     validations:
       required: true
 
   - type: textarea
+    id: plugin-and-datapack-list
     attributes:
       label: Plugin and Datapack List
       description: |
@@ -40,6 +47,7 @@ body:
       required: true
 
   - type: textarea
+    id: paper-version
     attributes:
       label: Paper version
       description: |
@@ -61,6 +69,7 @@ body:
     validations:
       required: true
   - type: textarea
+    id: plugin-version
     attributes:
       label: Plugin version
       description: |
@@ -80,6 +89,7 @@ body:
     validations:
       required: true
   - type: textarea
+    id: other-information
     attributes:
       label: Other
       description: |
@@ -89,6 +99,7 @@ body:
       required: false
 
   - type: markdown
+    id: pre-submission-checklist
     attributes:
       value: |
         Before submitting this issue, please ensure the following:

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -1,43 +1,51 @@
 name: Feature Request
 description: Suggest an idea for AntiRedstoneClock-Remastered
 labels: [ "status: needs triage", "type: feature" ]
+projects: ["OneLiteFeatherNET/6"]
+assignees: ["OneLiteFeatherNET/antiredstoneclock-remastered-triage"]
 body:
   - type: markdown
+    id: intro
     attributes:
       value: |
         Thank you for filling out a feature request for AntiRedstoneClock-Remastered! Please be as detailed as possible so that we may consider and review the request easier.
         We ask that you search all the issues to avoid a duplicate feature request. If one exists, please reply if you have anything to add.
         Before requesting a new feature, please make sure you are using the latest version and that the feature you are requesting is not already in AntiRedstoneClock-Remastered.
 
   - type: textarea
+    id: problem-context
     attributes:
       label: Is your feature request related to a problem?
       description: Please give some context for this request. Why do you want it added?
     validations:
       required: true
 
   - type: textarea
+    id: solution-description
     attributes:
       label: Describe the solution you'd like.
       description: A clear and concise description of what you want.
     validations:
       required: true
 
   - type: textarea
+    id: alternatives-considered
     attributes:
       label: Describe alternatives you've considered.
       description: List any alternatives you might have tried to get the feature you want.
     validations:
       required: true
 
   - type: textarea
+    id: additional-context
     attributes:
       label: Other
       description: Add any other context or screenshots about the feature request below.
     validations:
       required: false
 
   - type: markdown
+    id: search-reminder
     attributes:
       value: |
         Before submitting this feature request, please search our issue tracker to ensure your feature has not