refactor(cli): add fallback with husky git params to deprecation handling

[byCedric]

Description

This adds HUSKY_GIT_PARAMS fallback to the existing GIT_PARAMS deprecation handling, as described in their docs.

Note, I've created two solutions for this problem. This is one, and the other one is to remove (and later reimplement). Please pick one, I'll close the other.

Edit, I prefer this one since it's now backward compatible.

Motivation and Context

Usage examples

How Has This Been Tested?

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[byCedric]

There we go! Now it shouldn't be backward incompatible and doesn't require a major update 😄

[byCedric]

Ok, now it works fine I think. If GIT_PARAMS is used, but not defined, it falls back to the HUSKY_GIT_PARAMS check. If that is also not defined, the error is thrown. 😄

[byCedric]

I prefer to use this one over #499 because it's backward compatible.

[escapedcat]

If this works fine I would also use this over #499 👍

[marionebl]

OK, let's do this! :)