Implementing additional provider for Azure Storage Tables

Hi there,

I really like the approach via specification and thinking if it is possible to create a provider for Azure Storage Tables. My first guess was to align to the EFCore implementation, but indeed Storage Tables to not provide IQueryable to push the queries down to the data layer.

Obviously, it's not feasible to transfer the whole table content to create an IQueryable over the retrieved data.

So my questions are:

- Does it make sense and is it achievable to build an implementation besides EF?
- How would a starting point look like? As we have to translate the query and take care about PartitionKey AND RowKey. From my perspective, you do not necessarily have the partition key on an entity.

The issue names no files, tests, or entry points to begin from. First determine how the existing EF provider is structured and whether Azure Storage Tables can support the required query translation and PartitionKey/RowKey handling; done would require an agreed, feasible provider design.

Written by the indexing model from the issue text.