#107869Add option to not add cache busting to generated URIs
Description
The initial idea was to omit an option whether to add cache
busting for a generated URL or not and apply cache busting
everywhere. The reason for that was, that such specific option
might not be useful for other implementations of the URI generation
interface.
It turned out however, that there are legitimate cases where
not adding cache busting is required. Some of those are in code
that was touched already. For those a workaround for the missing
option was added, which was removing the query string. This workaround
is incomplete and also does not work when configuring versionNumberedFileNames.
Additionally, when generating URLs to JS assets, that already have a hashed
identifier in filename e.g. from a frontend build, adding additional cache
busting would not only be useless, it can also lead to unnecessary additional
requests, when the JS code itself required the same asset without TYPO3 cache busting.
On top of that, especially when imagining resources publishing to CDNs and generating
URLs for those, not only the cache busting option would be obsolete,
but also the “absolute” option, as URLs would have to be always absolute.
Also the the prefix option would be obsolete.
Last but not least, by implementing this option, the impact of
some changes could be lowered as well, having less required deprecations
and less breaking changes.