The TypoScript condition matching and our symfony
expression language handling is a heavily convoluted
mess: The entire API tends to fetch lots of global
state, the classes are complex, hard to understand and
handle, over-abstracted and full of anti-patterns.

The patch aims to mitigate this. The main strategy is
to provide relevant data from within callers directly
instead of fetching globals TYPO3_REQUEST, calling
GeneralUtility::_GP() and GeneralUtility::getIndpEnv().

* For TypoScript 'condition' expression handler usages,
  the frontend/backend related ConditionMatcher classes
  are obsoleted. The IncludeTreeConditionMatcherVisitor
  class within the new TypoScript parser is now the
  construct that prepares TypoScript relevant variables
  to initialize the symfony expression language construct,
  and gets variables actively hand over.

* The default provider now prepares variables from state
  that can be injected, the entire ProviderInterface no
  longer relies o...