Fix GIN index detection for views

[roji]

ToView mappings use view columns rather than table columns, so the index-aware array Contains translation did not find a modeled GIN index and fell back to ANY.

Inspect indexes through the column property's model metadata, which supports both table and view mappings while retaining the existing first-indexed-property and GIN-method requirements. Adds a focused ToView translation regression test.

Fixes #3829

[Copilot]

Pull request overview

Fixes PostgreSQL array Contains translation to detect modeled GIN indexes even when the entity is mapped via ToView(), by looking up indexes from the mapped CLR property’s model metadata rather than from table-only metadata. This ensures view-mapped queries can still translate to the @> containment operator (which can leverage the underlying index) instead of falling back to ANY.

Changes:

• Update GIN index detection for array-column Contains translation to work for both table and view mappings by inspecting indexes via the column’s mapped property metadata.
• Add a focused regression test asserting that ToView() mappings still translate Contains to @> when a GIN index is configured.

Show a summary per file

File	Description
test/EFCore.PG.FunctionalTests/Query/PrimitiveCollectionsQueryNpgsqlTest.cs	Adds a regression test covering ToView() + GIN index detection for array Contains translation.
src/EFCore.PG/Query/Internal/NpgsqlQueryableMethodTranslatingExpressionVisitor.cs	Adjusts GIN index detection logic to use property-based index metadata (works for views) instead of table index metadata.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Low

[Copilot]

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0 new
• Review effort level: Low