Users can create arbitrary range types, but Npgsql's EF Core type mapper currently doesn't look at the database to construct the mappings (singleton), making it impossible to know the datatype name for a given NpgsqlRange. What we can do is support the built-in range types, which will probably be enough.

Includes scaffolding support.