realpath() function returns a correct relative path but cannot resolve it in a symlink-based Apache configuration

[codeKerl]

I am encountering an issue with the realpath() PHP function within a symlink-based Apache configuration. While realpath() returns a correct relative path, it cannot resolve it further, likely due to Apache’s permissions being based on the symlink path.

The visible result of this issue is that the file Main.entry.js cannot be found, impacting application functionality. When omitting realpath() and using direct paths, both the local testing environment (using ddev) and the production environment work as expected without issues.

Classes/Service/ViteService.php -> Line 250

protected function determineAssetIdentifierFromExtensionPath(string $identifier): string
    ...
    $file = PathUtility::basename($absolutePath);
    $dir = realpath(PathUtility::dirname($absolutePath));
    ...

Actual behavior:
The function only returns a relative path, which cannot be further resolved, likely due to restrictions from Apache’s handling of symbolic links.

Please see corresponding pull request:
#93