feat: Migrate to v9

[kevintyj]

Migrates commitment to v9 (ESM support migration)

BREAKING!: Drops CJS support (will try to add CJS support again later)

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.83%. Comparing base (59797d1) to head (1ad28ed).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #13 +/- ## =========================================== - Coverage 100.00% 98.83% -1.17% =========================================== Files 4 4 Lines 123 172 +49 Branches 23 28 +5 =========================================== + Hits 123 170 +47 - Misses 0 2 +2 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[kevintyj]

Welp that was a nice try...

Edit: I may have over engineered the solution from the beginning, with all of the dependencies like ncc, cosmiconfig, v19 commitlint update, esm <-> cjs backwards compatibility, and a lot of other minor issues added a lot of unwanted complexity to the problem. The problem being why I had to be the one trying to parse the configuration file when there already are built in exported functions.

Solution: I will be releasing a breaking change v2 which will update the commitlint version to v19 as referenced to #12 as well as adding support for descriptions as referenced here: #11. However, this will drop the support for:

• Custom configuration file names:
  • This will be easily mitigated by the next solution offered in the section below, however, if you do really need support for custom commitlint specification file names such as my-awesome-config-file.jsx, either way you need to be setting up custom commitlint configurations on your environment (which I do not recommend you to do), you could easily just create a symlink pointing to a valid name such as commitlint.config.mjs, this action will be able to work in your workflow without any further setup.

Thats it. But to be honest, it was kind of the only feature as well... so... I came up with a compromise, which I genuinely think is a better solution:

• ESM & CJS configuration file compatibility
  • One of the main reasons why I had to make this tool (and initially, I thought it was only me and my company using it) was because there were no solutions out there that did this without any additional configuration step. This was important to a lot of our projects rely on CJS and ESM simultaneous support in a single repository because of miscellaneous dependencies and plugins. The up coming update will add zero config support for both ESM and CJS config files for commitlint.
• Automatic configuration detection
  • While support for custom configuration file names were dropped, I also discovered a neat little hidden gem in the commitlint repo to leverage their automatic configuration detection directly. This means that if you named your configuration files as one of the many options commitlint gives you, then this action will most likely work for you without any added configuration step at all. No inputs.
• Other little things like actions version upgrades, etc.

I will try to implement these features in the upcoming days will start raising new PRs