Template::redirect(): fix invalid DOM for AJAX & don't use JS for non-AJAX

Oops.  Invalid DHTML is still invalid, it's just harder to notice.
We shouldn't output a title element if the html is going to be inserted
into the body of another page.  (But we _should_ if the html is going to be
used as a standalone document).

We can try and fix this without changing existing code (including
out-of-tree code).  Change the response depending on whether the request
was made using AJAX.  We can serve the javascript without the title etc to
AJAX requests.  For non-AJAX requests, we can send a standard 302 redirect
and avoid the issue of valid html.

Using a 302 redirect allows writing front-end pages that work when JS is
disabled.
users auth restrict(): prevent infinite loop of Template::redirect()s

previous_page is broken in other ways (multiple tabs).  Still, if they hit
this specific bug they could get quite concerned, and it's easy enough to
suppress.

That said, if the redirect $url was passed by the caller, it's better not
to catch it here.  This will keep the loop obvious, so the caller can be
fixed.

This is distinct from an infinite loop of CodeIgniter redirect()s, in that
it doesn't use a standard HTTP redirect, where browsers would detect
excessive redirects and abort with an error message.
Allow confg_file helper to fail if config file does not exist in module directory, and fix events config looping causing event to load many times
Add docblock for config file paam added
database backup: fix yes/no options for languages other than English

The view sends translated values

    set_select('drop_tables', lang('bf_no')

the controller expects English only

    $add_drop = ($_POST['drop_tables'] == 'Yes') ? TRUE : FALSE;

Let's just use '0' and '1'.
database backup: fix gzip/zip options lest someone decide to translate them

No-one translated these, but if they had, it would have stopped it from
working.
permissions module: fix setting status for languages other than English
Merge branch 'develop' of github.com:ci-bonfire/Bonfire into develop
database backup: fix link to backup file in the status message

It didn't use site_url() to allow for subdirectory installs etc.,
and it tried to link directly to the file - which is forbidden by .htaccess
for obvious reasons.
database backup: .gzip doesn't work very well; use .gz instead

$ gunzip development_backup_2012-10-5_142207.gzip
gzip: development_backup_2012-10-5_142207.gzip: unknown suffix -- ignored

Shamefully, KDE's Ark is able to _open_ and list .gzip files, but then
chokes on extraction.  Presumbably it just runs gzip, although it didn't
bother showing me the error message.
Merge branch 'develop' of github.com:ci-bonfire/Bonfire into develop
Revert index.php from 2.1.2 - we need VIEWPATH

(It looks as if lonnie backported index.php).

VIEWPATH is used in application_helper.php.
This caused PHP errors in the Role form.
upgrade to jwerty 0.3.1

I found that creating a shortcut for '&' would kill keyboard input.
Upgrading to 0.3.1 seems to fix this.
Fix like statement in code builder permissions section

Addresses issue #611
Merge pull request #614 from mwhitneysdsu/develop

Fix like statement in code builder permissions section
users auth library: fix #616 - "remember me" causes fatal PHP error

Presumably triggered by f1ec67c0, "remove unecessary loader guards"
default theme: fix "remember me" in modal_login

"Remember me" was broken in modal_login.

Also it was enabled by default.  The main login page doesn't do that,
so we should be consistent and not do it here.
Updated to latest bootstrap
Updating to latest Bootstrap for admin theme.
Re-add Temporary fix to remove `array to string` conversion errors in PHP 5.4 until CI remember to backport it - fix #618

See https://github.com/EllisLab/CodeIgniter/issues/1273 for bug info

Unfortunately 2.1.2 had the same bug when we updated to it.