feat: add GitHub issue templates for new tests, test fixes, and new features

Author: MDUYN

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Documentation
+    url: https://github.com/coding-kitties/investing-algorithm-framework#readme
+    about: Check the documentation before opening an issue.

.github/ISSUE_TEMPLATE/new_feature.yml

@@ -0,0 +1,61 @@
+name: "✨ New Feature"
+description: Propose a new feature for the investing algorithm framework.
+title: "[Feature]: "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for suggesting a new feature! Please provide as much detail as possible.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem Statement
+      description: What problem does this feature solve? Why is it needed?
+      placeholder: I'm frustrated when ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed Solution
+      description: Describe the feature and how it should work.
+    validations:
+      required: true
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Framework Area
+      description: Which part of the framework does this affect?
+      options:
+        - Core (app, algorithm)
+        - Backtesting
+        - Data providers
+        - Order execution
+        - Portfolio management
+        - CLI
+        - Analysis / Reporting
+        - Infrastructure / Deployment
+        - Documentation
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: Have you considered any alternative approaches?
+    validations:
+      required: false
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Any mockups, reference implementations, or related issues.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/new_test.yml

@@ -0,0 +1,59 @@
+name: "🧪 New Test"
+description: Propose a new test case for the framework.
+title: "[Test]: "
+labels: ["test", "enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for helping improve test coverage! Please fill out the details below.
+
+  - type: input
+    id: module
+    attributes:
+      label: Module / Component
+      description: Which module or component should this test cover?
+      placeholder: e.g. app/algorithm, domain/models, services/order_service
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Test Description
+      description: Describe what the test should verify.
+      placeholder: Describe the behavior or scenario you want to test.
+    validations:
+      required: true
+
+  - type: dropdown
+    id: test-type
+    attributes:
+      label: Test Type
+      options:
+        - Unit test
+        - Integration test
+        - End-to-end test
+        - Backtest scenario
+    validations:
+      required: true
+
+  - type: textarea
+    id: acceptance-criteria
+    attributes:
+      label: Acceptance Criteria
+      description: What conditions must be met for this test to pass?
+      placeholder: |
+        - Given ...
+        - When ...
+        - Then ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Any additional information, links, or screenshots.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/test_improvement.yml

@@ -0,0 +1,68 @@
+name: "🔧 Test Improvement / Fix"
+description: Report a failing, flaky, or incomplete test that needs attention.
+title: "[Test Fix]: "
+labels: ["test", "bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Help us keep the test suite reliable. Describe the issue below.
+
+  - type: input
+    id: test-file
+    attributes:
+      label: Test File
+      description: Path to the affected test file.
+      placeholder: e.g. tests/app/test_backtesting.py
+    validations:
+      required: true
+
+  - type: input
+    id: test-name
+    attributes:
+      label: Test Name
+      description: Name of the specific test function (if applicable).
+      placeholder: e.g. test_backtest_with_limit_orders
+    validations:
+      required: false
+
+  - type: dropdown
+    id: issue-type
+    attributes:
+      label: Issue Type
+      options:
+        - Failing test
+        - Flaky / intermittent failure
+        - Incorrect assertion
+        - Missing edge case coverage
+        - Performance issue
+        - Test refactor needed
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Describe what's wrong and what the expected behavior should be.
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to Reproduce
+      description: How can someone reproduce the issue?
+      placeholder: |
+        1. Run `python -m pytest tests/...`
+        2. Observe ...
+    validations:
+      required: false
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Error output, logs, or screenshots.
+    validations:
+      required: false