[TASK] Deprecate callUserFunction "&" token for persistent objects

The method GeneralUtility::callUserFunction() method allows
to call "&" to put this logic into a "persistent" pool. We already
have the SingletonInterface which should be used for objects
that should be persistent.

Currently there are two "persistent object pools", one for
makeInstance and one for callUserFunc, which makes it very hard
to understand which object is used when. Reducing complexity
and using the SingletonInterface everywhere should be the best practice.

Resolves: #78733
Releases: master
Change-Id: I6d3c57056c2b5ab411a9b9f488dc48c757b4a148
Reviewed-on: https://review.typo3.org/50693


Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: TYPO3com <no-reply@typo3.com>