Add rate limiting for search

**Feature request**
It would be great to have retry for config.

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

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

First resolve the mismatch between the title's search rate limiting and the body’s config retry request. Then locate the configuration parsing and the relevant search or deployment entry point; no file or test is named in the issue. Done should include an agreed scope, the enable_retry default behavior, and tests covering the selected functionality.

Written by the indexing model from the issue text.