Improve the experience of working with spatial types using OData and EF Core

Related to [Issue #22951](https://github.com/dotnet/efcore/issues/22951)

Currently, EF Core recognizes spatial types based on the [NetTopologySuite](https://github.com/NetTopologySuite/NetTopologySuite) (NTS) while OData recognizes the types in [Microsoft.Spatial](https://docs.microsoft.com/en-us/dotnet/api/microsoft.spatial?view=odata-spatial-7.0). This means there is no "easy path" to using spatial with both EF Core and OData, but a complicated set of customizations like the ones described in [Customizing $filter for spatial data in ASP.NET Core OData 8](https://devblogs.microsoft.com/odata/customizing-filter-for-spatial-data-in-asp-net-core-odata-8/). .NET developers deserve a streamlined experience here.

There are two solutions @bricelam suggested:

1. The EF Core team provides a set of packages that enable use of Microsoft.Spatial types, so OData will "just work", or
2. The OData team provides an extension that recognizes NTS types, and EF Core will "just work"