Optimize middleware for large datasets

**Feature request**
It would be great to have search for components.

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

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

Start by locating the component-handling and configuration entry points in the repository, then trace how production deployments currently discover components. Define the behavior of the new enable_search option, including its false default, and verify that component search works when enabled without affecting the default path.

Written by the indexing model from the issue text.