Report better errors when unable to parse or execute TicketSQL

Tell the user that their query failed and provide the reason trimmed of
any stack trace.  Additionally, record any unparseable query in the logs
for the admin.

Previously parse errors were silent to the user and simply didn't return
any results.  Only the advanced query page reported errors.
Remove the query from the error message FromSQL reports

It is already included in the RT::SQL generated errors.
Don't bother rendering CollectionList when the query is unparseable

Avoids a double error message in the logs.
Enclose the query parse error in a red error box

For greater visibility that something ain't right.
Merge branch '4.0/report-ticketsql-errors' into 4.0-trunk