TYPO3 Core

Hi,

I noticed the following. All scheduler runs broke, when I switched the install base for a TYPO3 8.x project from composer

"require": {
        "typo3/cms": "^8.7",
                (...)

to the new modular structure:

"require": {
        "typo3/cms-about": "^8.7",
        "typo3/cms-belog": "^8.7",
        "typo3/cms-beuser": "^8.7",
        "typo3/cms-context-help": "^8.7",
        "typo3/cms-documentation": "^8.7",
        "typo3/cms-felogin": "^8.7",
        "typo3/cms-fluid-styled-content": "^8.7",
        "typo3/cms-form": "^8.7",
        "typo3/cms-func": "^8.7",
        "typo3/cms-impexp": "^8.7",
        "typo3/cms-info": "^8.7",
        "typo3/cms-info-pagetsconfig": "^8.7",
        "typo3/cms-rte-ckeditor": "^8.7",
        "typo3/cms-setup": "^8.7",
        "typo3/cms-sys-note": "^8.7",
        "typo3/cms-t3editor": "^8.7",
        "typo3/cms-tstemplate": "^8.7",
        "typo3/cms-viewpage": "^8.7",
        "typo3/cms-wizard-crpages": "^8.7",
        "typo3/cms-wizard-sortpages": "^8.7",
                (...)

Doing some investigation why the sudden breaking of all scheduler runs happened, reveals that it seems to be connected with the symbolic links being set using the typo3/cms package. When the scheduler is run, it looks for the autoload.php it does not find it, as it uses relative paths and wants to use the symlink route (which is shorter).
The difference in the installation was confirmed here: https://stackoverflow.com/a/51791055

The difference in the project setup would be fine, but the breaking schedulers caused by it, seem like a serious bug. Please check it out.