🛠 Repo: Remove husky for now

[voxpelli]

Tooling Suggestion Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest master branch of the repository.
• I have read and agree to Mocha's Code of Conduct and Contributing Guidelines
• I have searched for related issues and issues with the faq label, but none matched my issue.
• I want to provide a PR to resolve this

Overview

As mentioned in #5042 (comment), we decided to remove husky for now. Might re-add later.

Additional Info

No response

[JoshuaKGoldberg]

Err, remove or fix? My preference would be to use it to enforce formatting on Git commit, and remove any linting.

[JoshuaKGoldberg]

Explaining why I'm not in favor of this: Husky makes it a lot harder (admittedly, not impossible) to make commits locally that aren't well-formatted.

Not every contributor uses a nicely set up editor like VS Code with format-on-save. They might be new to development, and/or using something like Nodepad++, and/or just running with odd settings. For those edge cases, it's inconvenient to have to be told by CI that your change has formatting issues.

So from my perspective, there's very little downside to setting up formatting as a Git commit hook locally (node_modules/ is already going to be large; Knip recognizes properly set up Husky situations). And the upside is we have a bit more consistent, reliable of a dev experience - especially for new folks.

Which brings up a question: why do you two want to remove it? Assuming we're sticking to formatting on commit hooks and not linting or other more intrusive and/or time-intensive tasks... why not?

[voxpelli]

I use husky on all of my own projects so I’m totally up for keeping it. I can’t remember exact reason why we discussed dropping it