fix(workflows): use dotnet tool exec for .NET 10+ workflows

[DecSmith42]

Added conditional logic to use dotnet tool exec for workflows where .NET 10+ is detected, bypassing the need for redundant global tool installation. This improves efficiency and ensures compatibility with modern setups while maintaining fallback logic for older versions.

[Copilot]

Pull request overview

This pull request adds conditional logic to optimize GitHub Actions and Azure DevOps workflows when .NET 10 or higher is detected. Instead of globally installing the DecSm.Atom.Tool, workflows using .NET 10+ will use the more efficient dotnet tool exec command to run the tool directly.

Changes:

• Added version detection logic that checks if any SetupDotnetStep specifies .NET 10 or higher
• Implemented alternative workflow generation path using dotnet tool exec for .NET 10+ scenarios
• Maintained backward compatibility with fallback to global tool installation for older .NET versions

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
DecSm.Atom.Module.GithubWorkflows/Generation/GithubWorkflowWriter.cs	Adds conditional logic to use dotnet tool exec for GitHub Actions workflows when .NET 10+ is detected, with fallback to global tool installation for older versions
DecSm.Atom.Module.DevopsWorkflows/Generation/DevopsWorkflowWriter.cs	Adds conditional logic to use dotnet tool exec for Azure DevOps workflows when .NET 10+ is detected, with fallback to global tool installation for older versions

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.