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

Hi, team,

I noticed you are using _eslint-plugin-header_ with the schema-turn-off
workaround to support ESLint 9.

I forked _@tony.ganchev/eslint-plugin-header_ mid-2024 to address this
issue 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.

I've sent PR proposals to other projects in the cloudscape-design space:
- cloudscape-design/collection-hooks#136
- cloudscape-design/components#4308
- cloudscape-design/demos#243

Looking forward to your feedback.

Author: tonyganchev

eslint.config.js

@@ -3,7 +3,7 @@
 const eslint = require('@eslint/js');
 const tsEslint = require('typescript-eslint');
 const unicornPlugin = require('eslint-plugin-unicorn');
-const headerPlugin = require('eslint-plugin-header');
+const headerPlugin = require('@tony.ganchev/eslint-plugin-header');
 const prettierPlugin = require('eslint-plugin-prettier');
 const prettierConfig = require('eslint-config-prettier');
 

package-lock.json

@@ -32,6 +32,7 @@
   },
   "devDependencies": {
     "@testing-library/react": "^16.2.0",
+    "@tony.ganchev/eslint-plugin-header": "^3.3.1",
     "@tsconfig/node18": "^18.2.2",
     "@types/babel__core": "^7.1.16",
     "@types/glob": "^9.0.0",
@@ -42,7 +43,6 @@
     "@vitest/coverage-istanbul": "^3.0.7",
     "eslint": "^9.39.1",
     "eslint-config-prettier": "^10.1.8",
-    "eslint-plugin-header": "^3.1.1",
     "eslint-plugin-prettier": "^5.5.4",
     "eslint-plugin-unicorn": "^62.0.0",
     "husky": "^9.1.7",