This is the "approved" xUnit pattern, via:
https://github.com/xunit/samples.xunit/tree/master/DynamicSkipExample
It's also the only way I can make the damn skipping work...but at least
it's it's one-time code to make any server set relatively easily
skippable.

TODO: Figure out a clean way to disable this locally - we'll want this
functionality in the Core test suite as well as we add MySQL specific
tests (due to syntax differences in creating tables and such).

This fixes some MySQL issues - test suite that confirms issues and fixes
is incoming. TODO shortly after: implement the Insert<T, TKey> style
methods. I just want to get tests running (and some added) first.

Assuming the CHSARP30 were oversights here given the net35 removal, but
playing it safe and leaving for this commit.

Provided a name for MySql LAST_INSERT_ID call to allow the result to …

A full CoreCLR/DNX friendly conversion

Updated link to performance tests.

This eliminates the dual solutions and brings Contrib into the
project.json fold.
- Tests are ported to xUnit though SQLite is disabled on DNX due to
Issue #375 (Interop loads fail in the VS runner and  params are busted
regardless).
- Projects are consolidated down to what's currently possible with
project.json.
- Contrib moved to: Dapper.Contrib and Dapper.Tests.Contrib (so tests
appear at the end, no other reason vs. Dapper.Contrib.Tests)
- EF moved to: Dapper.EntityFramework(.StrongName)
- Rainbow moved to: Dapper.Rainbow
- SqlBuilder moved to: Dapper.SqlBuilder
- Packages are removed since it's not current-tooling friendly to keep
them (nor was it using them).
- xUnit implemented in Contrib via abstracts - this allow us to very
quickly add any database provider to the rig in a very concise way.
- Contrib unit tests fixed in various places - they were not
parallel-runner friendly
- Nuspecs removed, since they aren't used anymore (to eliminate
confusion)
- Removed speed tests for libraries that aren't on current versions of
.Net (what would we be comparing?)
- Perf tests moved to Dapper.Tests (consolidation from
Dapper.DNX.Tests), but aren't activated yet (no define)

Fixed missing check for explicit key in Contrib GetaAync()

hacky style - I think we want to remove the program given dnx run exists

This allows full testing from both solutions, all green.

This includes nuget updates for the test libraries but explicitly
excludes the npgsql upgrade, since there are known 2.0 vs. 3.0 driver
issues. If we can assume everyone is able to upgrade - then we should
switch testing over. Alternatively, we need to test both. My preference
would be the former.

This reverts commit 4a70b621.

Disable "Produce outputs on build" from test project; see https://github.com/dotnet/corefx/issues/4578

Update to rc1 (23516 dependencies); implement test skipping (including case-sensntivity check); swap all explicit #if to vague #if so we can iterate without bulk changes

Port tests to xUnit

There's a hit or miss on the dnx run style entry point now - but this
isn't really needed with dnx test, we can just drop the old code IMO.