Modify core data test helper for new tests
Fixes to CD test helper and fixing other tests

- Removing the reset of PSes for now. With concurrent writes/reads it causes many Core data code 134030 errors

- All AccountTests, BlogJetpackTests, EditPostViewControllerTests run

- CoreDataConcurrencyTest runs individually fine, but in the suite it becomes polluted by data from other tests (due to temp removal of hard reset)
Fix up more tests, keep other tests on main context

- Change context creation in ContextManager to avoid using dispatch_once, as it prevents recreation. ‘check and create’ should be the equivalent as before.

- Add a choice of context to WPAccount removeDefaultWPAccount with the default being the background context. The test should use the main context.

- Known issues: account tests cause exceptions due to a performBlock: save from another test in conjunction with the persistent store recreation. Cocoa error 134030.
Remove WPAccount from main on tearDown
Fix ReaderTest and fix crash on merging contexts
Add reciprocal concurrency test and fixes

- Rename ContextManager method for consistency

- Lock account creation (performBlockAndWait: does not block main thread in a test)
Add specific test for object permanence
Merge branch 'develop' of github.com:wordpress-mobile/WordPress-iOS into issue/634-coredata-tests

Conflicts:
	WordPress/WordPress.xcodeproj/project.pbxproj
	WordPress/WordPressTest/AccountTest.m
	WordPress/WordPressTest/CoreDataTestHelper.m
Fix tests from changes since merge
Fix up SettingsVCTest

- Manage Blogs was obsolete

- Prevent notifications on simulator (was causing the tests to fail, and should just be done anyways)
Removes some iOS7 forking code that is no longer needed.

Refs #677
Fix account removal with some tests

Because we destroy the contexts and PSC between tests, we must not remove the default account with a context which is tied to the OLD PSC. The cached __defaultDotcomAccount prevents other assert tests from passing.
Remove memory cached default account

Removing the core data account after reset will cause problems, removing the core data account and then reset is pointless as the entire core data stack is reset.
Use anonymous API for unauthenticated Reader

- There should definitely be a better check (issue #727 filed)
Wrap account post-creation with context block
Don’t pass a fake token for tests

- Causes ReaderPosts to be requested in authenticated mode, which causes issues/failures.
Use ContextManager throughout tests

- Missed one. Somehow this compiled before
Fix erroneous API switch
Clear in memory cache that caused merge conflicts

… between tests.
Remove useless context parameter