feat: Update husky pre-commit script to include ggshield

[mwisniewskiVSF]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSDoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2bc516b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sethidden]

@mwisniewskiVSF This repo is open source. Contributors outside VSF won't have ggshield. They can install it, but they still won't be able to ggshield auth login, thus creating an awkward situation when contrib ution. The contributors will be forced to always run git commit --no-verify to avoid it.

Can you please double check with stakeholders internally if we can include such an obtrusion to our open source repos?

[mwisniewskiVSF]

Agreed. We will not implement in the public OS repo.