Create SECURITY.md for security policy and reporting

[jarlungoodoo73]

Added a security policy document outlining supported versions and reporting procedures.

[Copilot]

Pull Request Overview

This PR creates a new SECURITY.md file to establish a security policy for the project, providing guidelines for supported versions and vulnerability reporting procedures. The file follows GitHub's standard security policy template format.

• Adds a new SECURITY.md file with security policy documentation
• Defines supported versions with a version support matrix
• Outlines vulnerability reporting procedures (placeholder content)

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

This instructional text should be replaced with concrete information about where to report vulnerabilities (e.g., security email, GitHub Security Advisories), response timeframes, and the vulnerability handling process.

Suggested change

	Use this section to tell people how to report a vulnerability.
	Tell them where to go, how often they can expect to get an update on a
	reported vulnerability, what to expect if the vulnerability is accepted or
	declined, etc.
	To report a security vulnerability, please use the [GitHub Security Advisories](https://github.com/OWNER/REPO/security/advisories/new) feature, or email us at [email protected].
	We aim to acknowledge receipt of your report within 2 business days. You can expect regular updates at least every 7 days while we investigate and address the issue.
	Once the vulnerability is confirmed, we will work to provide a fix as soon as possible and coordinate a disclosure timeline with you. If the report is declined, we will provide a clear explanation.