Urgent: Add GitGuardian Secret Detection Tool Pre-commit Configuration (RITM0296913)

[pre-commit-hook-update]

Dear Repository Owners,

This PR adds a .pre-commit-config.yaml file to the default branch of your repository. This file contains the configuration for our secret detection tool's pre-commit hook. This pre-commit hook will prevent commits containing sensitive secrets and protect Snowflake codebase.

Actions Required:

1. Please merge this PR into your default branch as soon as possible.
2. Propagate the changes in default branch to other remote and local repository branches as soon as possible, since presence of this file is required in all branches of your repository.
3. After pulling these changes into your local repositories (both existing and future ones), run the following command inside the local repository folder to install the pre-commit hook: pre-commit install
4. This pre-commit hook requires all the contributors to have a python library named "ggshield" to be installed in developer workstations, which IT has already installed. Only remaining task for each repository contributor is to run another command to authenticate this ggshield binary with the GitGuardian portal. Follow this guideline to complete the authentication step.

Note:

1. All the above steps are mandatory.
   2.For more information on how to use pre-commit hooks, please refer to our guideline.
   3.For any help reach out to: #gitguardian-secret-scanning-help.

[cla-bot-app]

Thank you for your submission–we really appreciate it! Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment in the below format.

I agree to the CLA

NOTE: Please make sure your email address is public, so we can verify your identity.

Steps to set your email address public:

1. Go to Email settings in your GitHub profile and uncheck "Keep my email addresses private" option
2. Then go to your GitHub public profile and choose your "Public email" from the dropdown
3. Next step is to save this setting by clicking "Update profile" button
4. Now comment I agree to the CLA in the PR comment section