C# 14 is bringing first-class spans, which changes the compiler resolution of method invocations, causes MemoryExtensions.Contains() (accepting spans) to be resolved instead of the traditional Enumerable.Contains. This can cause issues with LINQ providers, and likely would need reacting to in MEVD LINQ filters as well. We can integrate this logic into the FilterTranslationPreprocessor.
See dotnet/runtime#109757, and on the EF side, dotnet/efcore#35547 and dotnet/efcore#35100