Add rate limiting for monitoring

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

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

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

No files or tests are named. Start by locating the component configuration and monitoring or retry entry points, then determine how configuration defaults are defined. Done means a disabled-by-default enable_retry option exists and component retries are rate-limited as intended, with coverage for the configured behavior.

Written by the indexing model from the issue text.