Refactor validation for better readability

**Feature request**
It would be great to have filtering for hooks.

**Use case**
Many users need this functionality for production deployments.

**Implementation idea**
Add a new config option `enable_filtering` with default `false`.

No files or tests are named. Start by locating the hook configuration and execution path, then trace where hook selection occurs. Done means an `enable_filtering` option defaults to `false` and filtering behavior is covered by the relevant verification.

Written by the indexing model from the issue text.