Suppress exceptions on filter URL parameters parsing

[knstvk]

URL parameters are unreliable, they can be easily changed in such a way that the app will not be able to parse them correctly, for example when copy-pasting the URL.

Another case when a parameter cannot be parsed is when the filter contains a condition for a non-JPA entity and DataManager cannot load this instance by id (found when implementing #709).

Now FilterUrlQueryParametersSupport throws exceptions when it cannot parse the parameters or load entity instance, and these exceptions are shown to the user in the Unexpected Exception dialog.

I would suggest to suppress such exceptions and just print a message to the server log. The corresponding filter condition will just be cleared.