e.g. are we dropping script evals, or just the last n items in the profile?

Long overdue collapsing of the two suites

# Conflicts:
#	NRediSearch.Test/RediSearchTestBase.cs
#	NRediSearch/AggregationResult.cs
#	NRediSearch/AssemblyInfo.cs
#	NRediSearch/Client.cs
#	NRediSearch/NRediSearch.csproj

* start work on nreisearch aggregates

* port chunks of JRediSearch

* port the rest of aggregates and the highlight/summarize API

* Port QueryTest

* Import all of ClientTest from JRediSearch

* Add aggregate tests; normlaize tests

* NRediSearch : all tests passing

* add source prefix to a bunch of files

# Conflicts:
#	NRediSearch.Test/ExampleUsage.cs
#	NRediSearch/NRediSearch.csproj

* start work on nreisearch aggregates

* port chunks of JRediSearch

* port the rest of aggregates and the highlight/summarize API

* Port QueryTest

* Import all of ClientTest from JRediSearch

* Add aggregate tests; normlaize tests

* NRediSearch : all tests passing

* add source prefix to a bunch of files

This is both load and noise (and causes output truncation). This makes life a lot better for free.

Useful when hanging, but noisy when not. Disable for now, but leave in config for when needed readily.

Unsure why this fails on Appveyor...adding some logging.

Also removes the 4096 value and set it to always-zero, since that's the effective behavior until removal.

See https://github.com/dotnet/sdk/pull/2330 for details.

ensure that subscription connections are QUIT cleanly (interactive connections were already QUIT), *without* resurrecting like zombies

We're stable enough to not need this anymore, yay for faster runs!

As we go for green on the test suite, we'll want this checked in PRs and such. And in general DEBUG and RELEASE not matching is becoming a pain. Trying to minimize the differences.

This moves the socket bits all the physical connection which I think is a lot easier to grok than the double relationship between it and SocketManager. Pushing a PR for sanity check.

This is pretty much a boolean now...let's make it one. Also note PhysicalConnection is passes as `this`, it can't be null.

This helps for real-time output on long-running or hanging tests.

make sure there is only **one** path that can cause endpoints to be added, and ensure that the activation happens after the constructor - removes race condition that can lead to abandoned endpoints; note as part of this, switch the server-snapshot to span-based

This fixes net462, but not netcoreapp test hangs