chore: switch to @tony.ganchev/eslint-plugin-header

[tonyganchev]

Description

Hi, team,

I noticed you are using eslint-plugin-header on ESLint 8.

I forked @tony.ganchev/eslint-plugin-header mid-2024 to add support
for ESLint 9 and hoped it would be a temporary measure but since the
original has not been updated for five years I decided to continue
improving the new plugin and have been doing so for the last two years.

Specific improvements include:

• full JSON schema for validating the configuration.
• fixed multiple bugs with the behavior of the plugin on Windows.
• many other bug-fixes.
• improved autofixing and error-reporting behavior.
• added support for leading pragma comments before the header such as
  @jest-environment or eslint-env. In the case of the current
  review, this allowed me to remove the eslint-disable directive from
  one source and reintroduce validation for its header.

I switched the configuration to use the new config format for v3.2.x
as the leading comments feature is not supported by the array-based
format inherited from eslint-plugin-header.

I've sent PR proposals to other projects in the cloudscape-design
space:

• chore: switch to @tony.ganchev/eslint-plugin-header browser-test-tools#188
• chore: Switch to @tony.ganchev/eslint-plugin-header build-tools#38
• chore: switch to @tony.ganchev/eslint-plugin-header chart-components#185
• chore: switch to @tony.ganchev/eslint-plugin-header chat-components#121
• chore: switch to @tony.ganchev/eslint-plugin-header code-view#122
• chore: switch to @tony.ganchev/eslint-plugin-header collection-hooks#136
• chore: switch to @tony.ganchev/eslint-plugin-header component-toolkit#200
• chore: switch to @tony.ganchev/eslint-plugin-header components#4308
• chore: switch to @tony.ganchev/eslint-plugin-header demos#243
• chore: switch to @tony.ganchev/eslint-plugin-header documenter#112
• chore: switch to @tony.ganchev/eslint-plugin-header global-styles#73
• chore: switch to @tony.ganchev/eslint-plugin-header jest-preset#58
• chore: switch to @tony.ganchev/eslint-plugin-header test-utils#114
• chore: switch to @tony.ganchev/eslint-plugin-header theming-core#148

Looking forward to your feedback.

How has this been tested?

npm run lint

Review checklist

The following items are to be evaluated by the author(s) and the reviewer(s).

Correctness

• Changes include appropriate documentation updates.
• Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
• Changes do not include unsupported browser features, see CONTRIBUTING.md.
• Changes were manually tested for accessibility, see accessibility guidelines.

Security

• If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

• Changes are covered with new/existing unit tests?
• Changes are covered with new/existing integration tests?

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.11%. Comparing base (5ea6d7d) to head (879ecb4).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #401   +/-   ##
=======================================
  Coverage   95.11%   95.11%           
=======================================
  Files          67       67           
  Lines        3278     3278           
  Branches      702      702           
=======================================
  Hits         3118     3118           
  Misses        160      160           

☔ View full report in Codecov by Sentry.
📢 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.

[tonyganchev]

Can I ask @cansuaa or another maintainer help me retrigger the two flakes - or help troubleshoot the issues as they should not be related to the change in this PR. Thanks!

[cansuaa]

Can I ask @cansuaa or another maintainer help me retrigger the two flakes - or help troubleshoot the issues as they should not be related to the change in this PR. Thanks!

I'll take a look