docs: add license & readme file

[gowizzard]

Adds MIT License and Security Policy documentation to the project. Includes a new LICENSE.md and SECURITY.md in the repository.

[Copilot]

Pull Request Overview

This PR adds essential legal and security documentation to the project by introducing MIT License terms and establishing a security policy framework. The documentation provides clear guidelines for license compliance and vulnerability reporting processes.

• Adds MIT License with J&J Ideenschmiede GmbH copyright for 2025
• Establishes security policy supporting only the latest release version
• Defines vulnerability reporting process encouraging direct pull request contributions

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
LICENSE.md	Adds standard MIT License text with company copyright attribution
SECURITY.md	Establishes security policy with version support matrix and vulnerability reporting guidelines

[Copilot]

Encouraging public pull requests for security vulnerabilities is a security concern. This approach exposes vulnerabilities publicly before they are fixed, potentially allowing malicious actors to exploit them. Consider implementing a private disclosure process (e.g., security@company.com) or using GitHub's private security advisory feature instead.

Suggested change

	If you notice a security vulnerability, we encourage you to take an active role in our security process by directly creating a pull request with the necessary adjustments to address the issue. This proactive approach helps us ensure that vulnerabilities are swiftly resolved, maintaining the integrity and safety of our project.
	When creating a pull request to address a security vulnerability, please include:
	- A detailed description of the vulnerability and its potential impact.
	- A step-by-step guide to reproduce the issue, if applicable.
	- The specific changes you propose to mitigate the vulnerability.
	- Any additional information or context that might help in the assessment and resolution of the problem.
	This direct method of reporting and resolving security issues facilitates a more efficient and effective response, allowing us to implement security improvements with the help of our community. We appreciate your contributions to making our project more secure.
	If you discover a security vulnerability, we request that you report it privately to us to ensure it can be addressed before being disclosed publicly. Please send an email to `security@company.com` with the details of the vulnerability. Alternatively, you can use GitHub's private security advisory feature to report the issue securely.
	When reporting a security vulnerability, please include:
	- A detailed description of the vulnerability and its potential impact.
	- A step-by-step guide to reproduce the issue, if applicable.
	- Any additional information or context that might help in the assessment and resolution of the problem.
	We are committed to addressing security issues promptly and will work with you to ensure that the vulnerability is resolved effectively. We appreciate your efforts in helping us maintain the security and integrity of our project.