Follow up from !66995 - fix extra pagination component

The following discussion from !66995 (merged) should be addressed (related to #218252 (closed)):

• @pslaughter started a discussion: (+1 comment)

  here's the result after editing loadOverrides to introduce a Promise.reject randomly:

  20210812_fix_error_integration_override

  What's up with the extra pagination component on top?

  This is actually called out in our design system:

  Always anchor to the top of the list when the user interacts with the pagination component. Doing so reduces scrolling on the part of the user while keeping them on task.

  This doubling up the pagination component is a nice-to-have and we can handle in a follow-up if you prefer 😄