[Dev] Make nodejs pre-commit hook more resilient

[paulcam206]

Description

Fix up a small issue with the new pre-commit hook that I encountered -- it's possible to get into a state where the client hook is registered, but husky itself isn't installed:

1. cd source/nodejs && npm i
2. git clean -dxf .
3. touch ../android/commit-me.txt && git add --all && git commit -m "test commit"

At this point, the hook will execute, but since source/nodejs/.husky/_/husky.sh doesn't exist (wiped by git clean), the hook will fail here and prevent the commit.

The fix is to change the pre-commit hook to only apply if husky is in a good state.

Microsoft Reviewers: Open in CodeFlow

[ghost]

Hi @paulcam206. This pull request has had no recent activity for the past 5 days . Please take the necessary actions (review, address feedback or commit if reviewed already) to move this along.

[ghost]

Staleness reset by paulcam206

[paulcam206]

@licanhua - looks like the clang-format task is failing... why does it care about package-lock.json?

[licanhua]

@licanhua - looks like the clang-format task is failing... why does it care about package-lock.json?
I have PR #6869 to address the problem.
After clang-format check, I did git status -s check in https://github.com/licanhua/clang-format-launcher/blob/78be8a7d5d863797ed76e1ca2f348f592ba77734/src/index.ts#L187