Fixes #2178

Including translations

Closes #2059

Part of #2039

Also allow timestamptz literal SQL generation for DateTime.MinValue

Closes #2039
Closes #2043

Closes #2021

Even in non-legacy mode, to support migrating old models which still
require this mapping. Hopefully we'll be able to remove this in the
future (https://github.com/dotnet/efcore/issues/26168)

Fixes #1998
Co-authored-by: NShay Rojansky <roji@roji.org>

Closes #1970
Closes #873
Closes #473
Closes #1974
Closes #1983

Sync to EFCore 6.0.0-preview.3.21165.3
(3d6009b84224ba009143dfe8e08a4198acdc0afe)

Closes #1552

Closes #1567
Closes #1565

Closes #1294

Closes #854

(cherry picked from commit 6f347540)

Closes #854

Not done: Instant, ZonedDateTime and Period, which require features not yet
supported by the EF Core code generator.

Closes #713

(cherry picked from commit d6df46bf)

Not done: Instant, ZonedDateTime and Period, which require features not yet
supported by the EF Core code generator.

Closes #713

Done in EF Core c3991fd96, part of
https://github.com/aspnet/EntityFrameworkCore/issues/11896

- Properly quote schema and type name
- Respect default schema annotation
- Follows PR 605 (schema-scoped enums)

Notes:

* Added some missing NTS translations
* The new EF Core plugin model doesn't yet support specifying
  evaluatable (https://github.com/aspnet/EntityFrameworkCore/issues/13454),
  so we currently hack that up inside the main provider using type
  names as strings.

Fixes #658

When generating literal/constant representations of date/time types,
the microsecond component was mistakenly omitted.

Fixes #462

(cherry picked from commit 231b8887)

When generating literal/constant representations of date/time types,
the microsecond component was mistakenly omitted.

Fixes #462

Closes #333