Add CosmosStore Events in Tip support. Rename Stream->Decider

See CHANGELOG

Contributors: @enricosada @thinkbeforecoding @ylibrach

The emphasis of the V3 release is on the shift from Equinox.Cosmos (which was based on the closed source Microsoft.Azure.DocumentDb.Core package) to Equinox.CosmosStore (which is based on the Microsoft.Azure.Cosmos package).

CosmosStore notes

There are two key new features when one compares Equinox.CosmosStore with Equinox.Cosmos:

• events accumulate in the tip, reducing the document count in the store. In general this reduces overall RU consumption, but writes can cost more if you supply a large size limit when wiring up your CosmosStoreContext
• when creating a CosmosStoreClient, you can supply a secondary container, which enables one to have the proAchiver and proPruner templates
  1. archive to a warm store and
  2. prune from the hot store while
  3. the app falls back to the warm store if and only if it encounters events that have been migrated

NOTE: there are mild renaming changes when transitioning Equinox.Cosmos to Equinox.CosmosStore, but nothing that affects your implementation code.

Equinox.CosmosStore/Equinox.Cosmos stores are fully upward compatible.

NOTE Equinox.CosmosStore Events saved in Tip will not be visible to Equinox.Cosmos V2 users - if you need to be interoperable, you will need to set eventsInTip to 0

Added

• CosmosStore Replaced Equinox.Cosmos. See release notes for 3.0.0-beta1 through 3.0.0

Changed

• Equinox: Rename Equinox.Stream to Decider #272

Removed

• Cosmos