Align license references to Apache 2.0 across documentation

[Copilot]

Repository contains Apache 2.0 LICENSE file, but documentation inconsistently referenced MIT.

Changes

• README_v2.md: MIT License → Apache License 2.0
• docs/NEW_FEATURES_V4.md: MIT License → Apache License 2.0

README.md and pyproject.toml already referenced Apache 2.0 correctly.

Original prompt

The repository contains an Apache 2.0 LICENSE file, but several docs still reference MIT. Please update all visible license references to Apache 2.0.

Scope of changes:

• README.md: License section still says “MIT License” with link to LICENSE; change to Apache 2.0.
• README_v2.md: License section says “MIT License”; change to Apache 2.0.
• docs/NEW_FEATURES_V4.md: License footer says “MIT License - See LICENSE file”; change to Apache 2.0.
• pyproject.toml: license = {text = "MIT"} and classifier License :: OSI Approved :: MIT License; update to Apache 2.0 (e.g., Apache-2.0 text and License :: OSI Approved :: Apache Software License).

Acceptance criteria:

• All above files mention Apache 2.0 instead of MIT, with the LICENSE link kept intact where present.
• pyproject metadata reflects Apache 2.0 (license text + classifier).
• No references to MIT remain in these files.

Notes:

• LICENSE file is already Apache 2.0; do not change it.
• If you notice any other MIT mentions in the docs during the edit, switch them to Apache 2.0 as well.

This pull request was created from Copilot chat.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.