✨ Add Azure Cosmos DB provider (eQuantic.Core.Data.EntityFramework.CosmosDb)

[edgarmesquita]

What

Adds a new non-relational EF Core provider — eQuantic.Core.Data.EntityFramework.CosmosDb — for
Azure Cosmos DB, mirroring the existing MongoDb provider and slotting into the v5 family (per-major
8.x/10.x packaging).

Design

Cosmos via EF Core is a document store, so the provider builds on the base (not Relational) and only
overrides the four bulk operations Cosmos can't do server-side (ExecuteDelete/ExecuteUpdate are
relational-only):

• DeleteMany/DeleteManyAsync — load the matching documents, RemoveRange + SaveChanges; return
  the matched count.
• UpdateMany/UpdateManyAsync — extract the assigned members from the x => new T { … } expression,
  load the matches, and apply only those members to each (each value evaluated against the loaded
  entity, so x.Count + 1 works). Unassigned fields are left intact.

Everything else (Find/Insert/Execute, the QueryOptions → IQueryable translation) is inherited from
SetBase.

Partition keys

A Cosmos-specific QueryOptions extension so a read targets one logical partition instead of a
cross-partition scan:

new QueryOptions<OrderData>()
    .WithPartitionKey(tenantId)
    .Where(o => o.Status, FilterOperator.Equal, OrderStatus.Paid);

WithPartitionKey(string) is available on both net8 and net10; the 2- and 3-level hierarchical overloads
are net10-only (EF Cosmos 8 has no hierarchical API).

Packaging

• Per-major: 8.2.0 (net8, EF Cosmos 8.0.29) and 10.1.0 (net10, EF Cosmos 10.0.10) — same PackageId
  across lines, consistent with the family.
• Base InternalsVisibleTo extended to the new assembly (the set reaches the base's internal DbSet).
• Registered in the solution and the ci.yml/release.yml matrices (14 build / 4 test).

Tests (10, all green)

• CosmosUpdateExpression setter extraction — constant + entity-referencing values; rejects
  non-member-init / null.
• The four bulk ops via EF Core in-memory — including the guard that UpdateMany leaves unassigned
  members intact.
• WithPartitionKey registers a before-customization and chains.

Integration against a real Cosmos DB (emulator) is out of scope here: the bulk-op logic is exercised
through the in-memory provider, and WithPartitionKey's Cosmos-only execution is covered at the wiring
level. A Testcontainers/emulator suite is the natural follow-up (same gap noted for the other providers).

[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