Reorganize tests and remove redundant integration tests

[jbagga]

The tests are organized in a confusing structure and not as we usually organize them. There are a lot of redundant integration tests and some adapters lack unit tests.

1. This test suite can be used to ensure we are spec compliant. It can either be used to generate test code or parsed and tested.

• [x] 2. This folder has lots of integration tests for all operations (we should remove redundancy)
• [x] 3. Add integration tests for "Test" operation
• [x] 4. Clean up test object model classes - simplify by adding them to test classes that use them
• [x] 5. Ensure all test classes follow the Arrange, Act, Assert pattern; variable names are coherent/sensible (replace patchDoc with patchDocument, obj with object/targetObject etc.), remove unnecessary serialization and formatting of error messages
• [x] 6. ExpandoObjectAdapter and PocoAdapter do not have unit tests

This PR adds a new adapter called DynamicObjectAdapter with unit tests and integration tests in a folder called IntegrationTests.

cc @rynowak

[jbagga]

ExpandoObjectAdapter was combined with DictionaryAdapter, so now it has unit tests. See this

PocoAdapter unit tests were added here

[jbagga]

PR #117 cover 2., 3. 4. and 5.

[jbagga]

Shelving 1. for now. See #121