Switch the @ACL upgrade (which uses LoadSystemInternalGroup) to a sub

The LoadSystemInternalGroup which would be used believes that the 4.1.13
upgrade steps have already been run.  Obviously, they have not, leading
to failure to find the Privileged group.  Side-step this and use a
subroutine (which also must use DBIx::SearchBuilder::Record::LoadByCols,
or emit well-meaning warnings) to find the group and add the ACL.
Ensure that Scrip limits do not assume the current schema

LimitToQueue in 4.2 uses the ObjectScrips table, which does not exist as
of the 3.8.2 upgrade step.  Use the more specific Limit call to get the
RT 3.8 functionality.  Also, ensure that RT::Scrips does not attempt to
add a Disabled limit, which also does not come into the schema until
4.2.
Enumerate the relevant columns from the schema at the time

The current schema may have different columns, some of which did not
exist at the time.  Hard-code the set of relevant columns which existed
at the time.
Side-step the ObjectScrips code now found in RT::Scrip::Delete

The current code in RT::Scrip::Delete attempts to clean out records in
ObjectScrips -- a table which does not exist yet as of RT 3.8.3.  Step
around this by calling the DBIx::SearchBuilder::Record version of the
method.
Handle more formats of the Forward template.

The original version added in 3.7.15 said "This is forward...of a
ticket" which I changed in 3.8.6 when we split the Templates into
Forward and Forward Ticket.  However, I failed to account for the
missing newline and didn't go back and match the upgrade script with the
current initialdata.

This now matches on a user who installed or ugpraded from an early 3.8
as well as a user who installed on 4.0.

In either case, this is easily manually fixed, but we should try really
hard to fix it for the user.
$queue->Lifecycle is now the DB column, which is undef on upgrade

This caused a warning about comparing undef to 'approvals'.

When this script was originally written, Lifecycle was an object and
Lifecycle->Name was '' so it was safe.  With the change in 4.2 of
Lifecycle being the column, this started warning.
Merge branch '4.2/upgrade-from-3.8-errors' into 4.2-trunk