Numerous functions are wrapped in GeneralUtility/t3lib_div
since ages.
However, the API has grown and nowadays, one would simply
put this logic in one single API class. This makes testing much
easier and make the GeneralUtility methods much smaller.
In addition, some methods are even parked in e.g. ExtensionManager
where they don't belong.
The new lowlevel FileSystem API (which is not related to FAL)
class helps to have everything regarding file / folder reading
for the server system in one place.
This way, a lot of workarounds in EM can be overcome.
Goals of the new API:
* No static methods
* Speaking method names, that only do one thing
* No hooks, but Event Listeners.
* Exceptions and proper return types
* Type hinting