chore(deps): update dependency microsoft.codeanalysis.netanalyzers to 10.0.302

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
Microsoft.CodeAnalysis.NetAnalyzers (source)	10.0.300 → 10.0.302

---

Release Notes

dotnet/dotnet (Microsoft.CodeAnalysis.NetAnalyzers)

v10.0.302: .NET 10.0.10 / 10.0.302

You can build .NET 10.0 from the repository by cloning the release tag v10.0.302 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v10.0.301: .NET 10.0.9 / 10.0.301

You can build .NET 10.0 from the repository by cloning the release tag v10.0.301 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

---

Configuration

📅 Schedule: (UTC)

• 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 this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[samtrion]

Skipped by automated dependency-PR triage: build and tests pass, but the required "Run Tests / Testing .NET solution" check fails at the "Update codecov" step with gpg: Can't check signature: No public key. Retried once (re-ran the failed job) and it failed identically, so this looks like a systemic issue with the Codecov CLI's GPG signature verification (e.g. rotated/missing signing key) rather than a one-off flake tied to this dependency bump. Not force-merging since the required check is genuinely red; needs a workflow-level fix (e.g. pin an older Codecov CLI version or update the trusted GPG key) before dependency PRs can merge again.