TYPO3 Core

Follow up for #100282 #101871 #103898.

Scenario

Windows 10 with development mode set. LAMP stack using Docker Desktop.

Resulting symptoms
PHP in the docker container cannot resolve junctioned assets.

The resulting symlink viewed from docker is an absolute path wich does not exists inside the container.

Workaround
Running a powershell script replacing the Junctions by Symlinkd.

However, now composer complains.

 * Could not publish public resources for extension "typo3/cms-core" by using the "junction" strategy.
   Check whether the target directory "./html/_assets/1ee1d3e909b58d32e30dcea666dd3224" already exists
   and Composer has permissions to write inside the "_assets" directory.

Suggestion
On Windows, try symlinking, on failure, try junctioning. Maybe also save the symlinking failure if junctioning works during the execution.