chore: migrate HawkEye to v7

[tisonkun]

Which issue does this PR close?

N/A — this is a maintenance migration for the license-header tooling.

Rationale for this change

HawkEye v7 uses a new configuration schema and removes the v6 formatter exit-code behavior. The existing integration would stop working once v7 is installed.

What changes are included in this PR?

• migrate the HawkEye configuration to v7
• install the latest HawkEye release without pinning the tool version
• update the license-header helper for v7 formatter semantics
• normalize the small set of existing headers that v7 recognizes but rewrites canonically

Are these changes tested?

Yes. The repository license-header script passes with HawkEye v7 (1713 files, 0 changes, 0 conflicts, 0 unsupported). Changed YAML, TOML, Bash, and Python files also passed syntax or formatter checks as applicable.

Are there any user-facing changes?

No.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.37%. Comparing base (933710d) to head (8a50dee).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #24578      +/-   ##
==========================================
- Coverage   81.37%   81.37%   -0.01%     
==========================================
  Files        1116     1116              
  Lines      397661   397661              
  Branches   397661   397661              
==========================================
- Hits       323614   323597      -17     
- Misses      55106    55122      +16     
- Partials    18941    18942       +1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jayzhan211]

👍🏻