chore: install secret detection on pre-commit hooks

[zondervancalvez]

Commit to be reviewed

chore: install secret detection on pre-commit hooks

Primary Changes
----------------
1. Installed gitleaks for secret detection.
2. This pre-commit checker detects any secrets
or crypto so that it doesn't get pushed to
the github repo.

Fixes #2290

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[zondervancalvez]

[petermetz]

@zondervancalvez A good start, but please add an npm script in the top level package.json that coldstarts the pre-commit hook. The idea is that on-boarding new contributors could run that script ones and have the commit hook enabled after it finished running.

Please also add another npm script that removes the pre-commit hook and cleans up after itself (files downloaded/created during the enabler script )

You could call the scripts tools:install-pre-commit-secret-detection and tools:uninstall-pre-commit-secret-detection

[petermetz]

@zondervancalvez Are you still working on this?

[zondervancalvez]

@zondervancalvez Are you still working on this?

@petermetz Yes. I just prioritized the #3614