Make `contain_exactly` work with out of order hashes.

The reason that this was failing is that `contain_exactly` assumed that
its `expected` value was a matcher. As such it was using === to compare
the expected value with the actual value. This is completely correct for
matchers. However, when a hash is passed the implementation of === will
not match the actual value at all. Hash === won't invoke the RSpec
matchers.

This fix uses the lower performance values_match? which correctly
matches when hashes are provided.

Fixes #574.
Changelog entry for #578
Benchmarks on contain_exactly
Add a spec for in order hashes for contain_exactly
Implementation and spec cleanup for #578
Merge pull request #578 from rspec/fix-574

Make `contain_exactly` work with out of order hashes.