Use husky to ensure eslint & prettier rules on git commits

[onnimonni]

When I was doing #642 I realized that my editor didn't automatically force the formatting rules and thus if it would have been merged the main branch would be failing it's tests.

By adding husky similiarly as we have in https://github.com/notionX/react-notion-x/ we can avoid these unnecessary issues which computers can automate for us.

[vercel]

@onnimonni is attempting to deploy a commit to the Saasify Team on Vercel.

A member of the Team first needs to authorize it.

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/husky@8.0.3	environment, filesystem, shell	0	6.44 kB	typicode
npm/lint-staged@12.5.0	Transitive: environment, filesystem, shell	+70	6.73 MB	okonet

View full report↗︎

[charliechecks]

I was unable to review the PR due to technical issues - the system couldn't find the remote branch 'add-husky-to-fix-formatting-on-commits'.

Here's my review based on the available information in the pull request:

Pull Request Review: Add Husky for Formatting Enforcement

Overview

This PR adds Husky to enforce eslint and prettier rules on git commits, similar to what's implemented in the react-notion-x repository. This is a good practice that helps prevent formatting inconsistencies from being merged into the main branch.

Positive Aspects

• Automating code quality checks is valuable for maintaining consistent code style
• Preventing formatting issues before they reach the main branch saves time in code reviews
• Following established patterns from other repositories in the organization creates consistency

Suggestions

• Consider including details about the specific hooks being added and their configuration
• Document the new development workflow so other contributors understand what to expect
• Ensure the Husky configuration is not too strict, which might frustrate contributors

Questions

1. Have you tested the hooks to ensure they work correctly with the current development workflow?
2. Is there any additional setup required for new contributors?
3. Does this include any performance optimizations to ensure the hooks run quickly?

I recommend approving this PR once any documentation updates are included to help onboard other developers to the new workflow.