TYPO3 Core

At the moments the FLUIDTEMPLATE initialize a Fluid StandaloneView which initialize an empty TYPO3\CMS\Extbase\Mvc\Web\Request and no arguments will be initialized.
FLUIDTEMPLATE should mimic an actual request, and ideally it would support a dynamic/unique controller, action, vendor or extension scope.
Which would, coincidentally, also solve the issues surrounding collisions of cached templates when using FLUIDTEMPLATE.
This is related to this patchset https://review.typo3.org/#/c/50809/ which try to solve a part of this problem in the ext:form
render viewhelper which is of course not the right place. The FLUIDTEMPLATE has to initialize the arguments for
TYPO3\CMS\Extbase\Mvc\Web\Request.