make direct searches on users table case insensitive

Most columns in users table are text and we by default
should be case insensitive. Affects auto completion,
People tab and admin UI. Important on Oracle and Pg.
test case sensitivity in a few places

everything related to user searches, mostly
related to Pg and Oracle
Fix quoting in GetReferencedQueues to return useful keys in the hash

Previously, GetReferencedQueues returned queue names (including the
outer quotes, with internal escaping preserved) or possibly queue ids,
exactly as they were in the TicketSQL.  The code which used this return
value had to correctly strip the outer quotes, as well as remove the
escaping.  They chose to do this with a perplexing regex which worked
more by accident than anything else, and did the unescaping improperly
or not at all.

Standardize on returning the names in a manner suitable to be passed
unmodified to $queue->Load.
Only return queues which were referenced explicitly and positively

Previously, a TicketSQL query of << Queue != 'General' >> would
incorrectly limit the custom fields in the QueryBuilder to those on the
General queue.  Since limiting to only queues referenced with the '='
operator is nearly always more correct, only return those queues.  While
this is clearly insufficient to solve the more general problem (it still
fails on << Queue = 'General' OR Queue != 'General' >>, for example), it
in general produces more correct results.
Rename cfqueues parameter to imply its more general utility
QueryBuilder: Limit possible owners based on selected queues
QueryBuilder: Limit possible statuses based on selected queues
There is no reason to set date matches as case-insensitive

Modern DBIx::SearchBuilders ignore this at a low level, but there is no
reason to assert it in the first place.
Warnings avoidance when the session cleaner is run with --older

If --older is passed, the 'or' short-circuits the assignment of
$alogoff, causing "Use of uninitialized value" warnings when it is later
used.  Solve this by always pulling the AutoLogoff value before the 'if'
statement.
Error check files before calling scomp

Without this, adding a bad file path to CSSFiles or JSFiles will
cause RT to just die on page load.  Now we warn about the bad file
and continue serving RT.
make sure autocomp. for CF values is case insensitive
fix a warning "isn't numeric in numeric eq (==)"

items in @Default could be the class name instead of id.
e.g. this situation occurs in /Articles/Elements/QuickSearch
this warning can be reproduced by accessing links in "Quick search" box
of /Articles/index.html
it's not necessary or useful to duplicate color in color scheme

it seems very weird and wrong even for me, the original author.
Using loc'ed values as the key breaks callbacks in other languages

Removing the Advanced tab from searches would require doing it as
Advanced as well as Avanzado and Avancé.
Fix up the POD for rt-setup-database
Properly indent the body of DecodeMIMEWordsToEncoding

This commit changes only whitespace.
Test charset canonicalization for MIME words and charset aliases
Canonicalize charsets when decoding MIME words

We special case a few encodings, most notably GB2312, in order to handle
them correctly more often.  Extending this support to our MIME words
decoding means we don't fail to decode improperly marked Subjects,
attachment filenames, names in From or recipient headers, etc.

This bug was discovered because Outlook has a habit of sending email
with the body and MIME words marked as gb2312 even though the text
contains extended characters and is actually encoded in gbk or gb18030.
Modern RT properly decoded the body, but the subject and attachment
filenames were partially mangled.
Resolve aliases when canonicalizing encoding names

Resolving the aliases means we'll correctly decode more problematic
character sets.  For example, now we substitute gbk for gb2312 as well
as for euc-cn, gb2312a, gb-2312, etc.
There's no need to insert spaces into urls anymore

Since bd7b180 (3.9.4) we use word-wrap: break-word on the message body,
which lets the browser break lines in the middle of words if it needs
to.  This CSS property is a lot cleaner than shotgunning in spaces or
&shy; or <wbr> every so often, and has great browser support:

    https://developer.mozilla.org/en/CSS/word-wrap#Browser_compatibility

If the more general application of word-wrap: break-word ever goes away
on message bodies, we should apply it to links within the message body.