Injecting the base tag via a script causes assets to be requested once from an invalid url and then again from the correct one after the base tag got injected.
Setting it statically won't cause any problems with the servers subpath injection, because the browser will just use the first base tag in case there are multiple.
fixes#1096
The server doesn't inject the subpath anymore in case no path is set.
To handle this, the app needs to set the "base" element itself to ensure that the resources are requested from the proper path.
The old logic stringifyed all values, including strings, which caused problems with reading external stored values (e.g., mui-mode) via the "useStorage" hook.
