Create SECURITY.md for security policy

[talltechy]

Add a security policy document outlining supported versions and vulnerability reporting.

[Copilot]

Pull Request Overview

This PR adds a security policy document to establish guidelines for vulnerability reporting and supported version information. The SECURITY.md file provides a standardized template for communicating security practices to the project community.

• Adds a new SECURITY.md file with security policy template
• Includes supported versions table with example version ranges
• Provides placeholder guidance for vulnerability reporting procedures

---

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

[Copilot]

This placeholder text should be replaced with actual project-specific information about supported versions and security update policies.

Suggested change

	Use this section to tell people about which versions of your project are
	currently being supported with security updates.
	The following table lists the versions of this project that currently receive security updates. Only the latest minor releases in each major version are supported; all earlier versions do not receive security updates.

[Copilot]

This placeholder text should be replaced with specific instructions for vulnerability reporting, including contact information, expected response times, and process details.

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.
	If you discover a security vulnerability, please report it by emailing **security@example.com**.
	- We will acknowledge receipt of your report within **2 business days**.
	- You can expect a status update at least every **7 days** until the issue is resolved or closed.
	- We ask that you keep vulnerability details confidential until we have had a chance to address the issue.
	- If the vulnerability is accepted, we will work with you on a coordinated disclosure timeline. If declined, we will provide a clear explanation.