fix: move to node24

feat: enhance MSBuild setup summary in workflow 🛠️
- Added matrix strategy for multiple runners
- Improved summary output for MSBuild paths and architecture

README.md

@@ -9,7 +9,7 @@ This action will help discover where the `MSBuild` tool is and automatically add
 
 ```yml
 - name: Add msbuild to PATH
-  uses: microsoft/setup-msbuild@v2
+  uses: microsoft/setup-msbuild@v3
 
 - name: Build app for release
   run: msbuild src\YourProjectFile.csproj -t:rebuild -verbosity:diag -property:Configuration=Release
@@ -29,7 +29,7 @@ You may have a situation where your Actions runner has multiple versions of Visu
 
 ```yml
 - name: Add msbuild to PATH
-  uses: microsoft/setup-msbuild@v2
+  uses: microsoft/setup-msbuild@v3
   with:
     vs-version: '[16.4,16.5)'
 ```
@@ -42,7 +42,7 @@ If you need your Actions runner to target a pre-release version of Visual Studio
 
 ```yml
 - name: Add msbuild to PATH
-  uses: microsoft/setup-msbuild@v2
+  uses: microsoft/setup-msbuild@v3
   with:
     vs-prerelease: true
 ```
@@ -53,7 +53,7 @@ By default the action will use the x86 architecture for MSBuild, but it is possi
 
 ```yml
 - name: Add msbuild to PATH
-  uses: microsoft/setup-msbuild@v2
+  uses: microsoft/setup-msbuild@v3
   with:
     msbuild-architecture: x64
 ```
@@ -64,7 +64,7 @@ This makes use of the vswhere tool which is a tool delivered by Microsoft to hel
 
 ```yml
 - name: Add msbuild to PATH
-  uses: microsoft/setup-msbuild@v2
+  uses: microsoft/setup-msbuild@v3
   with:
     vswhere-path: 'C:\path\to\your\tools\'
 ```