[release/10.0] Fix snapshot generation for complex collection properties

[Copilot]

Fixes #37256

Description
Snapshot generation for properties in complex collections produces uncompilable code because it emits fluent API calls (HasMaxLength, HasPrecision, IsConcurrencyToken, ValueGenerated*) that don't exist on ComplexCollectionTypePropertyBuilder.

// Convention applies MaxLength to all strings
configurationBuilder.Properties<string>().HaveMaxLength(255);

// Generated snapshot fails to compile:
b.ComplexCollection(..., b1 =>
{
    b1.Property<string>("Name")
        .HasMaxLength(255); // CS1061: 'ComplexCollectionTypePropertyBuilder' does not contain 'HasMaxLength'
});

Customer impact
Customers using bulk configuration of these facets for all properties get compilation errors in their generated migration snapshot files. The workaround is to manually remove the unsupported fluent API calls from the generated snapshot.

How found
Customer reported on EF 10. This is expected to affect a small part of developers using complex collections.

Regression
No. It only manifests when a new EF 10 feature is used.

Testing
Tests added.

Risk
Low. The targeted fix is to just avoid emitting invalid code for the affected scenarios.

Original prompt

Fix #37256 by changing snapshot generation to ignore the annotations for which there are no methods on the configuration API for properties on a complex collection

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[AndriySvyryd]

@copilot Add a ModelDiffer test to check that no operations are generated when the model contains an annotation that's ignored in the snapshot

[Copilot]

@copilot Add a ModelDiffer test to check that no operations are generated when the model contains an annotation that's ignored in the snapshot

Added Noop_on_complex_collection_property_annotations_not_in_snapshot test in commit 2aa95cc. The test sets MaxLength on a string property in a complex collection (simulating convention behavior) and verifies no migration operations are generated since this annotation is ignored in the snapshot.

[AndriySvyryd]

@copilot Update progress by rewriting the PR summary using this template:

Fixes #{number}

**Description**
{Issue description}

**Customer impact**
{How does the reported issue affects customer's app? Are there workarounds?}

**How found**
{Was it customer reported or found during verification? How many customers are affected?}

**Regression**
{Is it a regression from a released version? Which one?}

**Testing**
{How the changes were tested}

**Risk**
{Low/Medium/High, argument why}

[Copilot]

@copilot Update progress by rewriting the PR summary using this template:

...

Updated the PR description with the requested template format.