Fix issue where post settings can get stuck in a refresh loop

Makes sure to be consistent in how we compare locations for a specific address.
Use NSInteger for type safety
Prompt the user if there is an error finding their location.
Always reset lastGeocodedLocation & address when getting current loc.
Use FormattedAddressLines instead of composing an address from properites.

Should be more reliable and prevent occurances of "(null)" in address strings.
Rely on placemark.name as a fall back just in case.
Don't include pending changes on note prune

For some weird reason, core data includes objects with pending changes,
even if they don't match the fetchLimit/fetchOffset conditions

Fixes #1623
Merge pull request #1627 from wordpress-mobile/issues/1616-postsettings-reloading

Fix issue where post settings can get stuck in a refresh loop
Merge pull request #1629 from wordpress-mobile/issues/1615-geolocation-fails-silently

Issues/1615 geolocation fails silently
Merge pull request #1637 from wordpress-mobile/issue/1623-disappearing-notes

Don't include pending changes on note prune
Merge branch 'develop' of github.com:wordpress-mobile/WordPress-iOS into issues/1327-reader-endpoints
BOOLs not NSNumbers
Use NSObjects instead of NSDictionaries to represent remote REST objects.

Gets ride of the NSDictionaries used to represent ReaderTopic and ReaderPost objects to the local services.
Instead uses plain objective c objects with properties.

Also cleans up a one sided relationship between ReaderPosts and Accounts that was missed in an earlier commit.
Tests for reader services.

This is a first pass at tests for the reader service.
It is not exhaustive.  Some things that could have been tested have been omitted
due to planned changes in the reader code, other things will be added over time.