[RFC] Optional per-repository consent before running local hooks

I’d like to propose an optional safety setting for Git hooks. When enabled, Git would check for an active hook before running it in a repository that the user has not approved. It would show the hook’s path and ask whether to run it once, trust the current hooks for this repository, or decline. This would help when a tool or setup step installs hooks from files supplied by a project. The check should happen immediately before execution, so it also covers hooks installed after a repository was cloned. For scripts inside the working tree, Git should ask again if the approved script changes. The default behavior could remain unchanged, with this protection enabled by an explicit user setting.