Move getTempFolder out of Core.php to own file
FIX Prevent DOS by checking for env and admin on ?flush=1 (#1692)
Merge pull request #2246 from hafriedlander/fix/flush_24

 FIX Prevent DOS by checking for env and admin on ?flush=1 (#1692) in 2.4
FIX: Have ParameterConfirmationToken includes work regardless of include path
FIX: Ignore invalid tokens instead of throwing 403
FIX: Actually use argument in getTempFolder
Merge pull request #2247 from hafriedlander/fix/flush_24

FIX: Have ParameterConfirmationToken work regardless of include path
FIX: Fixed TempPath inclusion for phpunit & cli-script
Split Core.php into Constants.php and Core.php and adjust main.php startup

The recent flush filter fix had a problem that you couldnt set a custom
BASE_PATH in _ss_environment because that file didnt get included until
after checking the confirmation token. This patch pulls the part of Core.php
that defines BASE_PATH into a seperate file that can be included earlier
in the startup sequence so that ParameterConfirmationToken can access it.

Core.php includes Constants.php with a require_once call, so for startup
scripts that dont pull in Constants.php themselves (like cli-script.php)
no change is needed.
FIX Only suppress fatal errors
Merge pull request #2254 from hafriedlander/fix/flush_24

Split Core.php into Constants.php and Core.php and adjust main.php startup
FIX Nice errors and allows flush on module removal
Merge pull request #2262 from hafriedlander/fix/flush_24

FIX Nice errors and allows flush on module removal
FIX: Fixed escaping of date in view of archived site.
FIX Flush on memory exhaustion and headers sent
FIX Token redirect where in IIS a / needs adding between host & url
FIX Constants magic_quotes needs function from Core
Merge pull request #2286 from hafriedlander/fix/flush_24

FIX Flush on memory exhaustion and when headers sent
composer/installers dep workaround

Moved to end of requirements, to work around a bug in composer - see https://github.com/composer/composer/issues/1147. This caused the dependencies to be installed in the wrong folder because the custom 'silverstripe-module' instructions hadn't been loaded at the time the core modules were installed via composer.
Removed composer dependency on CMS, workaround for composer/installers

The installer dependency gets included too late for 2.4,
so framework ends up in the wrong path. That's a bug with composer,
see See https://github.com/composer/composer/issues/1147
Until its fixed, we remove the explicit dependency which seems
to trigger this path in the dependency resolver (works for 3.x)