Refactor api 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`.

Start by locating the hook handling and configuration entry points in the Shell-based terminal agent. Trace how hooks are discovered or run, then determine how an enable_filtering option with a default of false should affect them. Done means filtering can be enabled through configuration while existing behavior remains unchanged by default.

Written by the indexing model from the issue text.