Build fails when BaseIntermediateOutputPath is absolute path (Stride.Core.Assets.CompilerApp.targets)

Release Type: Official Release

Version: 4.0.0.1-beta04-1347

Platform(s): Windows

Describe the bug
Build fails when $(IntermediateOutputPath) is absolute path

To Reproduce
Steps to reproduce the behavior:

1. Create Directory.Build.props file in parent directory with this:

<Project>
  <PropertyGroup>
    <BaseIntermediateOutputPath>z:\mydir\obj\$(MSBuildProjectName)\</BaseIntermediateOutputPath>
  </PropertyGroup>
</Project>

Expected behavior
Build from VS2019 succeeeds

Log and callstacks

4>C:\Users\ja\.nuget\packages\stride.core.assets.compilerapp\4.0.0.1-beta04-1347\buildTransitive\Stride.Core.Assets.CompilerApp.targets(81,5): error MSB3491: Could not write lines to file "C:\mydir\Stride\myapp.Stride.Windows\z:\mydir\obj\myapp.Stride.Windows\Debug\win-x64\stride\assetcompiler-uptodatecheck.inputs.expanded". The given path's format is not supported.

Idea for fix:

In Stride.Core.Assets.CompilerApp.targets, change this:

<StrideCompileAssetUpToDateCheckFileBase>$(ProjectDir)$(IntermediateOutputPath)stride\assetcompiler-uptodatecheck</StrideCompileAssetUpToDateCheckFileBase>

to this:

<StrideCompileAssetUpToDateCheckFileBase>$(IntermediateOutputPath)stride\assetcompiler-uptodatecheck</StrideCompileAssetUpToDateCheckFileBase>

Open Stride.Core.Assets.CompilerApp.targets around line 81 and reproduce the failure using the Directory.Build.props example with an absolute BaseIntermediateOutputPath. Check how the asset compiler up-to-date check path is assembled. Done means the project builds successfully from VS2019 without the unsupported-path error.