chore: automate release info updates

[scotluns]

Why

Release prep currently requires manually copying the latest ATT&CK version and six STIX SHA256 hashes into release_info.py. This adds a small updater so maintainers can refresh that metadata directly from the authoritative GitHub releases.

What Changed

• Added a release info updater that fetches STIX 2.0 hashes from mitre/cti and STIX 2.1 hashes from mitre-attack/attack-stix-data.
• Rewrites LATEST_VERSION, STIX20, and STIX21 via AST-backed source replacement, then runs Ruff formatting.
• Added tests for source rewriting and release asset name matching.

How To Verify

• uv run --extra dev ruff check scripts/update_release_info.py tests/test_release_info_updater.py mitreattack/release_info.py
• uv run --extra dev pytest tests/test_release_info_updater.py
• Verified v19.0 hash fetch restores the current release_info.py contents after simulating stale v18.1 metadata.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud