Handle invalid arguments better for paginated searches

## What?
When providing a invalid id to the search form of a overview page (e.g `id:not-an-id` or `count:not-a-number`) the user will see a notification with an 400 error invalid argument. We should catch that error and display a clearer message that the input cannot be parsed or understood.

## Why?
Right now it seems to the user that he encountered a bug, since no error handling took place.

## Your Environment
* Graylog Version: 4.0 and up