* Logging cleanup
* Cherry pick of Chbateys fix for watch/termination of entity
* When write is in progress or in batch queue message needs to go in buffer (If it doesn't it can re-order delivery)
* Possibility to prefer oldest in ddata writes and reads
* enabled for Cluster Sharding
* New ReadMajorityPlus and WriteMajorityPlus
* used by Cluster Sharding, with configuration
* also possible to define ReadAll in config
(cherry picked from commit 4ba835d328)
* Refactor shard to have a state for each entity
Rather than inferred from various maps and sets.
Unfortunately, we still have the by actor ref and by id but have moved
them to a class so they are always updated together.
* Avoid allocation on the message path
* Change Entities API to all OptionVals rather than a mixture
* Add spec for Entities
* Avoid multiple conversions of collection for handoff
* Migration from persistent shard coordinator to ddata with eventsourced remembered entities
* Fix bin compat in typed sharding
* Add log capturing
* Java API for nested case objects in typed sharding settings
* Starting some docs for remembering entities store
* Snapshot and marker to detect going back to persistence mode
* Review feedback
* Unused imports
* DData and Persistence based remember entitites refactored
* Order methods in the order of init in the shard.
* Some bad isolation between test cases causing problems
* Test coverage for remember entities store failures
* WithLogCapturing where applicable
* MiMa filters
* Timeouts from config for persistent remember entities
* Single method for deliver, less utf-8 encoding
* Include detail on write failure
* Don't send message to dead letter if it is actually handled in BackOffSupervisor
* Back off supervisor log format plus use warning for hitting max restarts
* actor/message based spi
* Missing assert that node had joined cluster
This removes the need to publish to a 'predictable' directory and then
'manually' rsyncing the locally-created repository from jenkins to gustav.
This is not needed for anything, it just simplifies the build a bit. We
could eventually use it for the paradox and api docs as well.
* Logging of toString of unknown classes should be avoided, since it could be huge
* Logging for EventSourcedBehaviorImpl includes the PersistentRepr,
for example:
```
Received Journal response: WriteMessageSuccess(PersistentImpl(Confirmed(2,q1,1583924066958),6,pid-6),,false,null,831cd256-9bc5-40e3-b84c-4a2d34dde643,0),9)
```
