Fix regression on CiviRules search due to exception handling

[eileenmcnaughton]

Overview

CiviRules is currently giving a fatal error on the civirules custom search. This is an Intra-rc regression found by @danielVV #11746 (comment)

Before

Fatal error on civirules custom search

After

custom search succeeds

Technical Details

When running CiviRules there is an incorrect sql query that runs in fillupPrevNextCache - a change in exception handling turned this into a fatal error. I've used the trapException parameter to make it non-fatal again.

Comments

I would prefer to have some sort of notice / deprecation warning when an invalid query is run here. If this were fixed in CiviRules then I think we could add that (seems like a bad idea when we know it will confuse rules users).

The issues with the query are
a) the alias for the contact table is contact not the usual (in our search framework) contact_a
b) it tries to order by rule_label and that fails (not quite sure why, I didn't dig).

ping @jaapjansma @ErikHommel -

Huge thanks for @danielVV for identifying the issue while in the rc stage

[jitendrapurohit]

Confirmed that this PR also fixes a DB fatal error on sorting with a custom field in Advanced Search results. Use case tested -

1/ Create a profile with custom field and add it to the search view.
2/ Search using the profile and sort with any custom field.

Before - DB error with no such field.
After - Works fine.

[adanielvv]

Tested on master.
Search works again with this PR.

The exception is still thrown, but ignored:
[info] Ignoring exception thrown by nullHandler: -19, DB Error: no such field

[eileenmcnaughton]

Thanks - the DB error was always there - the regression was that we stopped ignoring it :-)

[adanielvv]

Figured :)

[eileenmcnaughton]

Since 2 people have tested & this is a recent regression I'm going to merge based on those tests