Support different SQL translation when store representation has changed due to value conversion

[ajcvickers]

Consider cases like #10427 which involves SQL translations for DateTime calculations. If the property has been mapped to some non-datetime type, then this kind of translation will not work anymore. Instead, query should either:

• Do a different translation
• Revert to client evaluation

Probably client eval is what we can realistically do in the short term, but in the future it would be good to have the type mapping/value conversion participate in generating the translations.

[ajcvickers]

Triage: client eval for now.

[ajcvickers]

Triage: For 2.1, we will:

• Detect places where query is going to use a converted type in a place "that matters"--for example, Where clause--and output a warning.
• The warning will be for every operation other than equality/inequality
• The warning will direct people to consider client eval

For 2.1, we will not:

• Force client eval in these cases--for example, forcing client eval on all ordering would be bad since often only a stable ordering is needed and forcing client eval would kill perf
• Try to add API around this area since there are many considerations and there is not enough time to bake it for 2.1. See Support client evaluation when store evaluation is not appropriate #10265

[ajcvickers]

See also #11156