[Repo Assist] eng: fix global.json SDK constraint to accept any .NET 10.0 feature band

[github-actions]

🤖 This is a Repo Assist automated PR.

Summary

Fixes the global.json SDK version constraint so the project builds with any installed .NET 10.0 SDK, not just a specific future feature band.

Problem

The current global.json specifies "version": "10.0.200" with "rollForward": "latestMinor". This requires SDK 10.0.200 or higher to be installed. Since the currently released stable .NET 10 SDK is 10.0.102 (feature band 1), this causes dotnet commands to fail with:

A compatible .NET SDK was not found.
Requested SDK version: 10.0.200

This prevents local development and CI runs on machines that have SDK 10.0.1xx installed.

Fix

-    "version": "10.0.200",
-    "rollForward": "latestMinor"
+    "version": "10.0.100",
+    "rollForward": "latestFeature"

• version: "10.0.100" — Start of the stable 10.0 SDK releases (10.0.1xx)
• rollForward: "latestFeature" — Use the highest installed feature band within 10.0.x (accepts 10.0.102, 10.0.200, 10.0.300, etc. as each is released)

The previous latestMinor with 10.0.200 would allow any 10.x.x version. The new latestFeature with 10.0.100 is slightly more constrained (stays within 10.0.x) which is appropriate since the project targets net10.0. CI environments with SDK 10.0.200+ will continue to work unchanged.

Test Status

✅ Build: 0 errors, 208 warnings (all pre-existing)
✅ Unit tests: 235 passed, 0 failed (2 skipped — pre-existing)
⚠️ Integration tests: require live Swashbuckle test server — infrastructure, not related to this change

Generated by Repo Assist

---

Warning

🛡️ Protected Files

This was originally intended as a pull request, but the patch modifies protected files: global.json.

These files may affect project dependencies, CI/CD pipelines, or agent behaviour. Please review the changes carefully before creating the pull request.

Click here to create the pull request once you have reviewed the changes

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Generated by Repo Assist · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@4957663821dbb3260348084fa2f1659701950fef

[sergey-tihon]

Covered by #336