This change adds a secondary Console-specific Application
class, ExternalApplication, which can be created ad-hoc
from within third-party and TYPO3 binaries alike. When
used the ExternalApplication will bootstrap the TYPO3 env,
but will not process any request (this is the responsibility
of the third-party application using this bootstrapping).
Among other things this allows `./vendor/bin/fluid` to
render templates which use TYPO3 CMS ViewHelpers or
depend on TYPO3 environment variables, constants etc.
And this in turn allows the `--warmup` command from
Fluid to be used on nearly any Fluid template, whether it
exists in the core, in an extension or in fileadmin.
Usage: \TYPO3\CMS\Backend\Console\ExternalApplication::bootstrap
After running this in any third-party binary all TYPO3
configuration, constants, extension configuration etc. is
made available to all logic following that point.