OutPut the PathTooLong when when longpath is disabled

[JaynieBai]

Fixes #10201

Context

When build with dotnet sdk 9.0, during evaluation, it can't find the file Program.cs with main function

When build with MSBuild.exe, it has the following error

Changes Made

Throw the PathTooLongException exception in windows when the file path exceeds the maximum length
Catch the exception when evaluation and processing the msbuild.exe command.

Testing

Notes

[Copilot]

Pull Request Overview

This PR introduces a fix for handling long file paths when longpath is disabled by throwing and catching a PathTooLongException in key parts of the MSBuild process.

• Made IsPathTooLong public so it can be accessed from other components
• Added a check in WindowsFileSystem to throw a PathTooLongException when a directory path is too long
• Implemented catch blocks in XMake and Evaluator to handle and log the exception accordingly

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
src/Shared/FileUtilities.cs	Changed IsPathTooLong from private to public to allow external use
src/Shared/FileSystem/WindowsFileSystem.cs	Added a conditional check that throws a PathTooLongException if the path exceeds the maximum allowed length
src/MSBuild/XMake.cs	Added a catch block for PathTooLongException which writes the error message to the console
src/Build/Evaluation/Evaluator.cs	Added a catch block for PathTooLongException which logs the error message during evaluation

Comments suppressed due to low confidence (1)

src/Build/Evaluation/Evaluator.cs:351

• [nitpick] Consider including additional context in the error log to help with debugging long path issues instead of logging only the exception message.

ex.Message