main: re-enable the ComplexIndexes cross-tests and the joint smoke consumer against CodoMetis.EFCore.SchemaKit.PostgreSQL #333

Problem

On main, ComplexIndexesCrossTests and the fourth consumer in test/consumer-smoke-test.sh are off (net10.0 only), because EFCore.ComplexIndexes 5.x pins EF Core and Npgsql to 10.

Decided 2026-10-19 (CaffeinatedCoder/EFCore.ComplexIndexes#37): that package stays the EF Core 10 package. Its EF Core 11 successor is a new package, CodoMetis.EFCore.SchemaKit.PostgreSQL, starting at 11.0.0.

The integration csproj and the smoke script say "CaffeinatedCoder/EFCore.ComplexIndexes#42 restores them". An issue in that repository can't change this one, so this is the issue that does.

Change (main only)

release/10.x keeps EFCore.ComplexIndexes.PostgreSQL 5.4.x unchanged.

• Integration project: a test-only reference to CodoMetis.EFCore.SchemaKit.PostgreSQL with no TFM condition, using the namespace and wiring call SchemaKit ships.
• test/consumer-smoke-test.sh: the fourth consumer runs on net11 with the new id and is no longer skipped.
• Temporal claims: if SchemaKit: leave out what EF Core 11 and Npgsql 11 do natively; keep what stays unique EFCore.ComplexIndexes#39 leaves temporal constraints to Npgsql 11, then E48–E52 move to the native tests from Native temporal keys over ValueRanges columns on the 11 line: implement INpgsqlRangeTypeMapping, document WithoutOverlaps and WithPeriod #150, and the claims' quotes follow docs/efcore.md. Exclusion constraints and GiST indexes (E40–E43, E53) stay on SchemaKit.
• docs/efcore.md (11 line): SchemaKit for exclusion constraints and GiST indexes, native WithoutOverlaps/WithPeriod for temporal keys (Native temporal keys over ValueRanges columns on the 11 line: implement INpgsqlRangeTypeMapping, document WithoutOverlaps and WithPeriod #150). The main: say in the docs and the 11.0.0-preview changelog that EFCore.ComplexIndexes.PostgreSQL cannot be installed beside the net11 packages yet #322 sentence goes.
• The comments that cite Cross-tests with CodoMetis.ValueRanges on both lines: range and multirange columns as temporal-constraint periods and exclusion-constraint operands EFCore.ComplexIndexes#42 cite this issue instead, and main: claims.json names ComplexIndexesCrossTests as holding 11 claims, but the test is compiled out on net11 #321's record of the gap goes.

Blocked by

• CodoMetis.EFCore.SchemaKit 11.0.0-preview.1 on nuget.org (SchemaKit 11.0.0-preview.1: the first slice of the new API, on EF Core 11 / Npgsql 11 under the new ids EFCore.ComplexIndexes#38)
• the temporal decision in SchemaKit: leave out what EF Core 11 and Npgsql 11 do natively; keep what stays unique EFCore.ComplexIndexes#39
• Native temporal keys over ValueRanges columns on the 11 line: implement INpgsqlRangeTypeMapping, document WithoutOverlaps and WithPeriod #150