Fix relation enumeration naming for 0.10 (breaking change)

[bazer]

IImmutableRelation<T> enumerates rows, but its AsEnumerable() instance member returns primary-key/row pairs and hides the standard LINQ extension. The same-looking call therefore changes both the element type and loading timing unexpectedly.

This PR renames that member to AsKeyValuePairs() on the public interface, runtime implementation, and existing mock. Standard LINQ relation.AsEnumerable() now exposes the existing row sequence without loading at the call. AsKeyValuePairs() retains the previous keyed behavior, including possible synchronous loading and dictionary construction.

This is an intentional breaking change for 0.10. Consumers must recompile, pair-consuming calls must use AsKeyValuePairs(), and custom implementations must implement the renamed member. Audit inferred calls even when they still compile: they can now yield rows instead of pairs. No obsolete alias is retained because it would continue hiding the standard extension.

The PR contains only the runtime rename and regression coverage. Async implementation, package changes, and the ongoing planning/migration documentation are excluded. The existing mock's unimplemented operations remain outside this change.

Validation:

• Interface and concrete row-view binding, I/O-free view construction, empty relations, keyed lookup identity, and composite keys: 8/8 focused compliance cases passed across SQLite file and in-memory targets.
• DataLinq runtime builds passed for net8.0, net9.0, and net10.0 with zero warnings/errors.
• git diff --check passed. Validation ran against the matching source files in the existing checkout; the three transferred PR files were compared with those files before committing.
• Server-backed provider runs and packed ApiCompat verification were not run for this narrow change.

Commands run from the repository root:

.\scripts\dotnet-sandbox.ps1 run --project src/DataLinq.Testing.CLI --no-build -- run --suite compliance --targets 'sqlite-file,sqlite-memory' --filter '/*/*/MultipleForeignKeyRelationTests/*' --output failures
.\scripts\dotnet-sandbox.ps1 run --project src/DataLinq.Testing.CLI --no-build -- run --suite compliance --targets 'sqlite-file,sqlite-memory' --filter '/*/*/EmployeesRelationAndThreadingTests/Relations_*' --output failures
.\scripts\dotnet-sandbox.ps1 run --project src/DataLinq.Dev.CLI --no-build -- build src/DataLinq/DataLinq.csproj --no-restore --output summary

Related to #107; this does not complete the async workstream.

[bazer]

Code review of 3d054cb912f9b448f6e4a686dba3535929f37d30 against PR base 2a58a19a9ef2ec38cfbc1d303bd3c70c63515869.

Findings: No actionable correctness defects found in the reviewed changes.

Checked the interface, runtime implementation, and mock rename; LINQ extension binding; lazy row-view construction; and keyed/composite-key access. The loss of the old member and the changed binding of inferred AsEnumerable calls are intentional 0.10 compatibility changes documented by this PR. The regression tests cover both row and key/value enumeration.

Validation: Static source review and regression-test inspection. I did not rerun this PR's test matrix during this review.