chore(deps): update microsoft.aspnetcore to 9.0.11

[thomhurst]

This PR contains the following updates:

Package	Type	Update	Change
Microsoft.AspNetCore.Mvc.Testing (source)	nuget	patch	9.0.10 -> 9.0.11
Microsoft.AspNetCore.OpenApi (source)	nuget	patch	9.0.10 -> 9.0.11
Microsoft.AspNetCore.TestHost (source)	nuget	patch	9.0.10 -> 9.0.11

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[claude]

Claude finished @thomhurst's task —— View job

---

Pull Request Review - Microsoft.AspNetCore 9.0.11 Update ✅

Review Tasks:

• Examine modified files for dependency version updates
• Assess compatibility and breaking changes
• Review security implications
• Check performance considerations
• Evaluate test coverage needs
• Provide final recommendation

Files Reviewed:

• Directory.Packages.props - Central package management file
• TUnit.Templates/content/TUnit.AspNet.FSharp/TestProject/TestProject.fsproj - F# template
• TUnit.Templates/content/TUnit.AspNet/TestProject/TestProject.csproj - C# template
• TUnit.Templates/content/TUnit.AspNet/WebApp/WebApp.csproj - Web app template

Review Findings:

✅ Code Quality & Best Practices

• Excellent: Uses centralized package management via Directory.Packages.props
• Consistent: All three ASP.NET Core packages updated to the same version (9.0.11)
• Clean: Template projects properly reference the centralized versions

✅ Compatibility & Breaking Changes

• Safe Update: This is a patch version bump (9.0.10 → 9.0.11) within the same major/minor version
• No Breaking Changes: Patch updates in .NET typically contain only bug fixes and security patches
• Consistent Pattern: Other recent commits show similar dependency updates (EntityFrameworkCore, DependencyInjection)

✅ Security Considerations

• Positive: Patch updates often include security fixes - this should be merged promptly
• Low Risk: Microsoft ASP.NET Core has a strong security track record
• Scope Limited: Only affects testing infrastructure and web templates, not core TUnit functionality

✅ Performance Considerations

• Neutral/Positive: Patch updates may include performance improvements
• Minimal Impact: These are testing and template dependencies, not runtime dependencies for end users

✅ Test Coverage

• Adequate: No test updates needed for patch version dependency updates
• Template Verification: The modified templates will be tested through template verification processes
• Integration Testing: Existing ASP.NET integration tests will validate compatibility

Final Recommendation: APPROVE ✅

This is a clean, low-risk dependency update that follows best practices:

1. Safe Change: Patch version updates are typically safe and contain important security/bug fixes
2. Proper Management: Uses centralized package versioning correctly
3. Consistent Approach: Follows the same pattern as other recent dependency updates
4. Automated Quality: Renovate bot has configured automerge, indicating confidence in safety

Suggested Action: Approve and allow automerge to proceed.