chore: add remove-finalizers hook and update module-sdk to v0.7.0

[duckhawk]

Description

Unify the module delete hook (030-remove-finalizers-on-module-delete) and update module-sdk to v0.7.0.

Changes:

• Renamed hook from 030-remove-sc-and-secrets-on-module-delete to 030-remove-finalizers-on-module-delete
• Unified hook logic: removes finalizers from Secrets, ConfigMaps in module namespace; StorageClass (if controller creates them); all CR resources from module's crd folder
• Updated module-sdk from v0.2.0 to v0.7.0
• Added CRGVKsForFinalizerRemoval and WebhookConfigurationsToDelete to consts

Build fixes (commit 2):

• Updated sds-common-lib to v0.0.0-20250428090414-0c2938b30fa7 (new kubeclient API without kubeconfigPath)
• Fixed go.sum for module-sdk v0.7.0 (go mod tidy)
• Added sds-common-lib and kubernetes-csi/external-snapshotter deps for sds-* and snapshot-controller modules

Gitleaks (commit 3):

• Added .gitleaks.toml with allowlist for known false positives (docs, patches, test files)
• For csi-ceph: replaced Ceph userKey example in docs with placeholder

Why do we need it, and what problem does it solve?

• Ensures clean module deletion by removing finalizers that block resource deletion
• Aligns all CSI/SDS modules with the same hook implementation
• Updates module-sdk to the current version for compatibility and security
• Enables secret scanning with gitleaks while filtering false positives

What is the expected result?

• Module can be deleted without resources stuck in Terminating state due to finalizers
• All modules use consistent finalizer removal logic
• go build ./... in hooks/go passes for all modules
• gitleaks detect passes for all modules

Checklist

• The code is covered by unit tests. (N/A - hook logic)
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.