Update Microsoft.Extensions to 10.0.10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
Microsoft.Extensions.Caching.Memory (source)	10.0.1 → 10.0.10
Microsoft.Extensions.Configuration.Binder (source)	10.0.1 → 10.0.10
Microsoft.Extensions.Http (source)	10.0.1 → 10.0.10

@Lombiq/open-source-orchard-extensions-renovate-notification-recipients

---

Release Notes

dotnet/dotnet (Microsoft.Extensions.Caching.Memory)

v10.0.10

v10.0.9

v10.0.8

v10.0.7

v10.0.6

v10.0.5

v10.0.4

v10.0.3

v10.0.2

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 06:59 AM, only on Thursday (* 0-6 * * 4)
• 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.

[github-actions]

This pull request appears to contain breaking changes.

• If you can do this without breaking changes, then please do that, it'd be better.
• If breaking changes are inevitable, then add an explanation of these and a migration guide for users to the description of the pull request (during the next release, these will be added to the release notes). A CompatibilitySuppressions.xml file was generated for each project with breaking changes that you can download from the artifacts and use to suppress further such warnings.
• If the changes are technically breaking but not something that would actually be breaking for consuming projects (like the signature of a constructor changing due to new injected dependencies) then also take the generated CompatibilitySuppressions.xml file and add the ignore-breaking-changes label too, the push another commit. Furthermore, consider how in the future this can be avoided: Can perhaps the class be made internal (what's usually better for implementations of interfaces for injected dependencies)?