Handle edge cases in filtering

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

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

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

No file, test, or entry point is named. Start by locating the config parsing and filtering code, then determine what pagination applies to, how pages are requested, and how production deployments should configure it; done should include documented behavior and tests for the default-disabled option and edge cases.

Written by the indexing model from the issue text.