docs: improve API rate-limit error handling in table-http-example

[devversion]

There are currently three issues with the table-http-example:

1. If a user hits the rate limit within this example, an overlay
   will be displayed mentioning the rate limit issue. This overlay
   intends to overlap the whole table, except for the paginator. Right
   now this is broken as there is a minium height throwing off the
   assumption that the paginator is at the bottom of the example.

2. If a user hits the rate limit, the paginator length is reset to
   zero. This means that the user is unable to trigger new requests
   as the previous/next page buttons become disabled.

3. Due to incorrect error handling, the observable will be
   replaced by a new one that will always return an empty list.
   The rate limit/API errors should be caught within the switch
   map to not prevent future API requests on errors.

Updated StackBlitz: https://stackblitz.com/edit/angular-vf4jjs?file=src/app/table-http-example.ts

Fixes #11547.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}