Cosmos: Modernize materializer & subdocument projectionbinding

[JoasE]

• Materialize query results using Utf8JsonReader
• Bind projections of embedded types and remove client projection distinct limitations
• Remove __jObject backing property
• Require projecting out primary key values for owned projections using AsNoTrackingWithIdentityResolution
• Throw for any undefined non-value projection (Cosmos: Anonymous and dto projections filter undefined implicitly when projecting a single property #38298 (comment))
• Truncate floating point numbers when materializing to fixed point types instead of rounding (Cosmos: Materializer rounds when deserializing floating point numbers as fixed point numbers #38138)

Part of: #34567
Implements: #34067
Fixes: #38138 , #31696

[JoasE]

Tests are failing for linux emulator because the projection order is not preserved there, and the materializer currently depends on this order. This is specifically usefull in NoTrackingWithIdentityResolution cases, where we materialize the id of the root document first before materializing sub documents. Production cosmos does preserve the projection order, but I'm wondering whether this is something we should depend and whether it's a guarantee in cosmos or might be subject to change. Regardless, I've created: Azure/azure-cosmos-db-emulator-docker#335
@AndriySvyryd Thoughts on this?
PS: PR still WIP, needs some cleanup but is close to final form

This appears to have been be planned by the linux emulator team

[Copilot]

Pull request overview

Copilot reviewed 100 out of 104 changed files in this pull request and generated 4 comments.

Files not reviewed (1)

• src/EFCore.Cosmos/Properties/CosmosStrings.Designer.cs: Generated file

[Copilot]

Pull request overview

Copilot reviewed 100 out of 104 changed files in this pull request and generated 2 comments.

Files not reviewed (1)

• src/EFCore.Cosmos/Properties/CosmosStrings.Designer.cs: Generated file

[Copilot]

Pull request overview

Copilot reviewed 100 out of 104 changed files in this pull request and generated 1 comment.

Files not reviewed (1)

• src/EFCore.Cosmos/Properties/CosmosStrings.Designer.cs: Generated file

[Copilot]

Pull request overview

Copilot reviewed 100 out of 104 changed files in this pull request and generated 2 comments.

Files not reviewed (1)

• src/EFCore.Cosmos/Properties/CosmosStrings.Designer.cs: Generated file

[AndriySvyryd]

@AndriySvyryd Thoughts on this?

You can skip these for the Linux emulator for now. But if they say that this is by design we'll have to rethink our approach.

[Copilot]

Pull request overview

Copilot reviewed 100 out of 104 changed files in this pull request and generated 3 comments.

Files not reviewed (1)

• src/EFCore.Cosmos/Properties/CosmosStrings.Designer.cs: Generated file

[Copilot]

Pull request overview

Copilot reviewed 100 out of 104 changed files in this pull request and generated no new comments.

Files not reviewed (1)

• src/EFCore.Cosmos/Properties/CosmosStrings.Designer.cs: Generated file

Comments suppressed due to low confidence (1)

src/EFCore/Storage/Json/JsonReaderData.cs:89

• In stream mode, the leftover-buffer logic uses buffer.Length rather than _bytesAvailable to determine how much valid data remains after totalConsumed. If a stream read returns fewer bytes than the buffer length (common near EOF and possible with non-buffered streams), this will copy uninitialized/stale bytes and overstate _bytesAvailable, corrupting subsequent JSON parsing.