OverrideOutgoingMailFrom: Use $CorrespondAddress if the queue's isn't set

Otherwise the meaning of the Default key changes depending on the
queue's correspond address being set or not.  Using the global
correspond address for queues with no specific correspond address, as
well as moving the Default check into the else branch, means the Default
key is only used when there's no ticket involved.  This is the
documented behaviour in RT_Config.pm.
SetOutgoingMailFrom: Accept an email address as a value and use it globally

Covers the simple case of sending all bounces to a specific address,
without the only previous solution of resorting to defining all queues
in OverrideOutgoingMailFrom.  Any definitions in the Override option
still take precedence.
Explicitly force 404s on non-WebPath requests

Because the DocumentRoot is set to share/html, a request for /index.html
with WebPath set to /rt still _succeeds_, and presents the Mason source
for share/html/index.html

Add an explicit rewrite rule to 404 anything which is not under the
WebPath.
Warn on failures to create RT::URI::* resolver objects

Otherwise compilation errors and the like are hidden in $@ never to be
seen by human eyes.

Errors locating the RT/URI/*.pm file itself are ignored so as not to
fill the logs with noise on normal http, https, ftp, etc. links.
Remove never used fields on Scrips

ConditionRules and ActionRules were introduced by 1037b076 but remained
unused.  They appear to be an unfinished thought related to scrips and
approvals and have nothing in common with modern Rules despite sharing
the same moniker.
Merge branch '4.0/outgoing-mail-from' into 4.0-trunk

Conflicts:
	etc/RT_Config.pm.in
Upgrade notes for the Set/OverrideOutgoingMailFrom changes
Make sure that On Create we notify Ccs and other recipients

Otherwise the ticket create form is a partial lie.  I'm not sure how
this wasn't noticed for so long.

This probably also wants an upgrade step, but I'm not sure of the best
way to do that at the moment.
Add a Notify Owner and AdminCcs action

Combining notification of Owner and AdminCcs into the same action
receives the benefit of duplicate recipient squashing if the Owner is
(as commonly is the case) a queue-level AdminCc.
Notify Owner too on Create and Correspond, not just AdminCcs

Otherwise Owners who aren't a queue AdminCc (or also a ticket level
AdminCc) don't receive mail!

This needs a smart upgrade path, similar to 63852e9, which adds the
action if it doesn't exist already and modifies the default scrips if
they still exist.  It also needs a note in UPGRADING-4.2.
Add the new action "Notify Owner and AdminCcs" on upgrade

Rather than try to automatically upgrade scrips, make a note of the
changes and let admins manually update if they'd like.
Document behavior of testfile option
Merge branch '4.0/log-resolver-failures' into 4.0-trunk
Merge branch '4.0/document-testfile-delete' into 4.0-trunk
set with_disabled_column in classes where it is missing

Set with_disabled_column in classes that have a disabled column in
the database but the flag is missing in the collection class.

The following classes will NOT get with_disabled_column set even
though the corresponding database table has a disabled column:

RT::Tickets
- Will be dealt with in 4.2 by dropping the column

RT::CachedGroupMembers
- all use cases of this lib need reviewed before adding

RT::ObjectCustomFieldValues
- Will be dealt with in 4.2 by renaming the flag.

See issues:20766
Fix a pod formatting error
Fix a file path, and use F<> to refer to files
"RT" and "rt" are valid local links when generating documentation
Print DatabasePort as well as DatabaseHost in rt-setup-database

Signed-off-by: Thomas Sibley <trs@bestpractical.com>
Merge branch '4.0/devel-apache-404s' into 4.0-trunk