[PP-2] Add paging to Component "Audit" operation content listing

Overview

In 📌 Calculate field and component dependencies on save and store them in an easy to retrieve format Active we added a new Component audit controller that lists usage of components in content entities.
This can easily be a big listing, so it should have a pager.

Proposed resolution

• Add paging for content entities listing in Component audit controller. We should only need one pager, as the other listings in that page aren't that expensive to build, and potentially won't have that many listed items.

Postponed on 📌 Calculate field and component dependencies on save and store them in an easy to retrieve format Active itself, and 📌 [PP-1] Evaluate storing XB field type's "deps_*" columns in separate table Active which should improve its performance (if needed).

User interface changes

Component audit contains a pager for the content entities listed.