[QoL] Skip pre-commit on merge and rebase, add pre-push

[OrangeRed]

What are the changes?

Update lefthook config so it isn't as disruptive.

Why am I doing these changes?

To open a discussion as to what is the most ergonomic way to use git hooks.
Running eslint every time we merge or rebase the newest changes from main feels bad

What did change?

Lefthook config options

Screenshots/Videos

N/A

How to test the changes?

Checkout the branch and make some dummy commits / merges / rebases

Checklist

• There is no overlap with another PR?
• The PR is self-contained and cannot be split into smaller PRs?
• Have I provided a clear explanation of the changes?
• Have I tested the changes (manually)?
  • Are all unit tests still passing? (npm run test)
• Are the changes visual?
  • Have I provided screenshots/videos of the changes?

[OrangeRed]

@Greenlamp2 Do you think the pre-push hook is worth keeping if we run the pre-commit hook on (almost) every commit?

[Greenlamp2]

@Greenlamp2 Do you think the pre-push hook is worth keeping if we run the pre-commit hook on (almost) every commit?

i think at some point we should replace completely the pre-commit by a pre-push