Remove emysql from dialyzer deps
Remove DB_TYPE parameterization of itests: pgsql only

Since we are now focused on supporting postgres, we can simplify the
integration test code to not require a DB_TYPE environment variable to
be set for running the tests.
Run itests via non-verbose eunit

It's easier to identify and diagnose failures without the verbose
output.
Fix update_cookbook_version_checksums test: compare sorted results
Fix update_cookbook_version_checksums_with_shared_checksums test pass

I'm unclear at what point this became broken. As far as I can tell,
the test itself was not testing a valid construct. What we're trying
to test is that in the face of multiple versions with overlapping
checksums, the checksum cleanup behavior when one of the existing
cookbook versions is updated.

For this test we have:

cbv-06
  checksums: shared-1, v6-1, v6-2
cbv07
  checksums: shared-1, v7-1, v7-2

In the test we update cbv07 and set its checksums as:

cbv07 (updated)
  checksums: v7-3, v7-2

So we expect:

  Added: v7-3
  Deleted: v7-1
Cleanup cbv version tuple access in itest
Extract user related itests into chef_sql_users

The itests module is too large. This patch begins the process of
extracting out related test code into smaller modules.
Move clients itests to chef_sql_clients
Extract data_bag and data_bag_item itests to separate modules
Extract nodes itests to separate module
Extract sandbox itests to separate module
Extract cookbook related itests into modules and util helper module

This one was rather tangled and so lands as a single commit. We could
likely improve the organization. But at least things are in small
enough chunks to make it easier to digest individual tests.
Cleanup application config setup in itest
Fix fetch_latest_cookbook_versions tests (they were quite broken)

First, make the tests actually run. A generator form of the assert
macro was used such that these tests were not being run.

Secondly, the helper function to generate the expected results was
returning an empty list.

Rather than mess with generating, the expected result from the specs,
simply hard-code the expected values. This makes the tests easier to
understand and keeps the implementation simple.
Merge branch 'sf/fix-itests'