Suppress CA1707 warnings for test method names

[Copilot]

Build was failing with 80 CA1707 warnings from test method names using underscores (e.g., Constructor_WithNullHttpClientFactory_ThrowsArgumentNullException).

Changes

• Added <NoWarn>$(NoWarn);CA1707</NoWarn> to test project configuration

<PropertyGroup>
  <TargetFramework>net9.0</TargetFramework>
  <!-- ... -->
  <!-- Suppress CA1707: Underscores in test method names are acceptable for readability -->
  <NoWarn>$(NoWarn);CA1707</NoWarn>
</PropertyGroup>

Underscores in test method names follow the Method_Scenario_Expected pattern used throughout the test suite. Suppression scoped to test project only.

Original prompt

look at the last build-and-test output and resolve all the dotnet warnings. the build should have zero warnings when completed.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[Copilot]

Pull request overview

This PR resolves build failures caused by 80 CA1707 analyzer warnings from test method names using underscores. The solution suppresses CA1707 specifically for the test project, preserving the established Method_Scenario_Expected naming pattern used throughout the test suite.

Changes:

• Added <NoWarn>$(NoWarn);CA1707</NoWarn> to the test project configuration with explanatory comment

[github-actions]

🏗️ Terraform Plan

🌍 Environment: dev

✅ Validate — Passed

✅ Plan

✅ No changes. Your infrastructure matches the configuration.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud