Nuget packaging strategy and implementation

[rofr]

Design and implement nuget packaging and naming strategy. We want a core package with 0 dependencies besides NET Standard. Memstate.Core is not a good name, it can be confused with dotnet core. How about Memstate.Minimal?

Modules could have Module in the name. For example:

• Memstate.Modules.EventStore
• Memstate.Modules.Postgres

And an easy to get started, single package with everything bundled. This package would also contain versions verified to work together. What would be a good name?

What about 3rd party contributions? Memstate.Contrib.*?

[rofr]

Good enough for now, landed with: Simple 2-part names for the core packages:

• Memstate.EventStore - EventStore storage
• Memstate.Postgres - PostgreSQL Storage
• Memstate.Wire - Wire Serializer
• Memstate.JsonNet - Newtonsoft JSON Serializer
• Memstate.Core - core library with engine, server and client
• Memstate.Host - Service host for running in a standalone process
• Memstate.AppMetrics - Metrics implementation
• Memstate.Bundle - Everything in a single nuget package