Add rate limiting for notifications

**Feature request**
It would be great to have analytics for lib.

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

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

No file or test is named; start by locating the existing configuration handling and the notification or analytics entry points. First clarify whether the request is notification rate limiting or an analytics toggle, then verify that the agreed behavior is implemented and that the new option defaults to false.

Written by the indexing model from the issue text.