chore(deps): update dotnet monorepo to 10.0.12

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
Microsoft.Extensions.Configuration (source)	10.0.11 → 10.0.12
Microsoft.Extensions.Configuration.Abstractions (source)	10.0.11 → 10.0.12
Microsoft.Extensions.DependencyInjection (source)	10.0.11 → 10.0.12
Microsoft.Extensions.DependencyInjection.Abstractions (source)	10.0.11 → 10.0.12
Microsoft.Extensions.Http (source)	10.0.11 → 10.0.12
Microsoft.Extensions.Logging.Abstractions (source)	10.0.11 → 10.0.12
Microsoft.Extensions.Logging.Console (source)	10.0.11 → 10.0.12
Microsoft.Extensions.Options (source)	10.0.11 → 10.0.12
Microsoft.Extensions.Options.ConfigurationExtensions (source)	10.0.11 → 10.0.12
System.Security.Cryptography.Pkcs (source)	10.0.11 → 10.0.12

---

Release Notes

dotnet/dotnet (Microsoft.Extensions.Configuration)

v10.0.12

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

[argus-pr]

✅ Reviewed 08be606 — nothing to flag.

🤖 @argus-pr — automated AI assistant; replies may be wrong.

[argus-pr]

@argus-pr review — 08be606 · model deepseek-v4-flash-vision-exp

Summary — This pull request bumps ten Microsoft.Extensions.* and System.Security.Cryptography.Pkcs packages from 10.0.11 to 10.0.12 in Directory.Packages.props, a routine Renovate dependency update with no code changes.

Risk surface — facts about this change, not findings. A reviewer should start here:

• Dependency changes: dependency manifest(s) changed — verify added/updated dependencies — Directory.Packages.props.

No issues found at or above the MEDIUM threshold. ✅
That is this review finding nothing on the risk surface above — not a finding that there is nothing there.

Severity	Posted	Suppressed
CRITICAL	0	0
HIGH	0	0
MEDIUM	0	0
LOW	0	0

What this review did — 1 of 1 pass(es) over 1 file(s)

• Passes completed: 1 of 1
• Files reviewed: 1 of 1
• Tool calls made while investigating: 0

What it chose to check — the panel's own reading of what mattered here, planned before it looked. Feedback for a reviewer, not a guarantee that each check was completed:

• Fetch the exact diff for Directory.Packages.props to see which versions changed and confirm the change is limited to the 10.0.11→10.0.12 bump (via get_pr_diff for Directory.Packages.props)
• Read Directory.Packages.props at head to verify all entries are consistent, no duplicates, and the file structure is intact (via read_file Directory.Packages.props)
• Grep the repo for any other references to these package versions (csproj, lock files, other props) that might need to stay in sync (via grep for 'Microsoft.Extensions.Configuration' and 'System.Security.Cryptography.Pkcs' and '10.0.11' across the repo)
• Confirm the projects actually reference these packages and that the bump doesn't break the multi-targeting (netstandard2.1/net8.0/net10.0) — e.g., check csproj files for PackageReference entries (via grep for PackageReference in src//*.csproj and tests//*.csproj)

---

🤖 Reviewed by @argus-pr (AI, model deepseek-v4-flash-vision-exp) — automated, may be wrong. Reply @argus-pr help for commands.