chore: added ci/cd templates & details

Author: Maximus7474

.github/FUNDING.yaml

@@ -0,0 +1,2 @@
+github: [Maximus7474]
+ko_fi: maximus_prime

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,16 @@
+---
+name: 🐛 Bug report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+## Description
+## Reproduction Steps
+## Expected Behavior
+## Environment Info
+- **OS:** [e.g. Windows 11, Ubuntu 22.04]
+- **Version:** [e.g. v1.0.4]
+
+## Additional Context

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,12 @@
+---
+name: ✨ Feature request
+about: Suggest an idea for this project
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+---
+
+## Problem Statement
+## Proposed Solution
+## Alternatives Considered
+## Additional Context

.github/ISSUE_TEMPLATE/security_report.md

@@ -0,0 +1,22 @@
+---
+name: 🛡️ Security Report
+about: Report a security vulnerability privately
+title: '[SECURITY] '
+labels: security
+---
+
+> [!CAUTION]
+> **STOP! Do not post sensitive security vulnerabilities in a public issue.**
+> To keep our users safe, please report all security concerns through our private advisory channel.
+>
+> **[Submit a Security Advisory →](https://github.com/fxManagerProject/fxManager/security/advisories/new)**
+
+
+---
+
+## Why use an Advisory?
+* **Privacy:** Only maintainers can see your report.
+* **CVE ID:** We can request a CVE ID directly through the advisory.
+* **Collaboration:** We can collaborate on a fix in a private fork before going public.
+
+*If you believe the issue is not a security risk but a general bug, please use the **Bug Report** template instead.*

.github/ISSUE_TEMPLATE/support_request.md

@@ -0,0 +1,11 @@
+---
+name: ❓ Support Request
+about: Need help using the project?
+title: '[SUPPORT] '
+labels: support
+assignees: ''
+---
+
+## What are you trying to achieve?
+## What have you tried so far?
+## Relevant Logs / Screenshots

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,39 @@
+## Description
+
+<!-- REQUIRED !!
+
+	Please address the following:
+	* Purpose of the PR (resolves issue #X, adds feature, improves X functionality)
+	* Mention how the PR implements/integrates the feature/fix/improvement
+	* Mention any related Issues if applicable
+
+ -->
+
+<!--
+	Answer truthfully, this has it's purpose when reviewing PRs
+	and is not used to judge the contributor's work.
+	Lying on this is pointless, and we allow ourselves to not consider
+	PRs where GenAI was used and not declared.
+-->
+- [ ] Generative AI was used in the creation of the changes of this PR.
+
+---
+
+## Tests
+
+- [ ] Tested in development mode
+- [ ] Passes typecheck
+- [ ] Builds & runs on Windows
+- [ ] Builds & runs on Linux
+
+---
+
+## Additional Notes
+
+<!--
+	Any extra details you wish to share, i.e.:
+	* Unable to test on linux -> state why for context
+	* Request feedback
+	* Explain why the PR is listed as a Draft
+	* List todo steps requiring discussion
+-->