[TASK] Avoid ObjectManager in ext:fluid ViewHelperResolver

Finish the ObjectManager usages in ext:fluid. With #94285
we made the ViewHelperResolver a singleton service, which
is not ok since it holds state: Namespaces are added at
runtime and they additionally depend on request.
The solution is similar to RenderingContext from #94285
though: Have a factory to create fresh instances for
each parsing cycle for this failsafe mode enabled class.
View helper instance prototypes itself are then retrieved
using GeneralUtility::makeInstance().

Resolves: #94292
Related: #94285
Related: #90803
Releases: master
Change-Id: I08018b57e3bd5b293be999d7c5415578604c7897
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69419


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benni Mack <benni@typo3.org>
Tested-by: Benjamin Franzke <bfr@qbus.de>
Reviewed-by: Benni Mack <benni@typo3.org>
Reviewed-by: Benjamin Franzke <bfr@qbus.de>