Updated CocoaLumberjack

Cocoapods keeps trying to update it when changing other stuff, so update
it on a separate commit in preparation for some other pod changes
Drop duplicate SFHFKeychainUtils instances
Revert "Removed extra instance of SFHFKeychainUtils"

This reverts commit 137f0afa58ceb7563a54be204ec1ca5679a87c2d.
Fixed references to SFHFKeychainUtils
Migrate keychain credentials on launch

Mae sure any keychain item with the kSecAttrAccessibleWhenUnlocked is
updated to kSecAttrAccessibleAfterFirstUnlock so we don't break when
waking up from a notification

fixes #306
Merge pull request #314 from wordpress-mobile/feature/credentials-fix

Fixes keychain access
#312 - Added a simple method to remotely turn on & off email support

Uses http://api.wordpress.org/iphoneapp/feedback-check/1.0/ to determine if feedback is turned on or off.
Ignore invalid device orientations on rotation

It's kind of a hack, but we're getting rid of panels/sidebar on #333, so
a major refactor there is not worth it.

fixes #328
Merge branch 'release/3.8.4' of github.com:wordpress-mobile/WordPress-iOS into release/3.8.4
#312 - Turn feedback on by default if problems happen when checking
#312 - Eliminated use of obscure ternary operation for nil check
#312 - Replaced instance variable with property for better scoping
Merge pull request #337 from wordpress-mobile/issues/312

#312 - Added a simple method to remotely turn on & off email support
#312 - Use feedbackEnabled accessor for consistency
#312 - Tweak cache and defaults for feedback

- Use default cache policy, we’ll tweak cache-control on the server
- Register defaults so the feature will be enabled initially
Updated SFHFKeychainUtils

I got a crash running the tests when WPAccount passed a nil error.

I updated the code to match the latest pod, then added back our `kSecAttrAccessible` changes.

The getter method is also aware of `kSecAttrAccessible` now, which might fix some problems:

- storeUsername: would call getPasswordForUsername: first to see if it’s a new password or needs update
- if a valid password was found it’ll be returned even if it used anything other than kSecAttrAccessibleAfterFirstUnlock
- storeUsername: specifies kSecAttrAccessibleAfterFirstUnlock in the query for SecItemUpdate, so the password wouldn’t be updated

This shouldn’t really be a problem after the keychain fix on the app delegate, but it’s more correct. And the fix is meant to be temporary anyway.
Merge pull request #342 from wordpress-mobile/sfhfkeychainutils-update

Updated SFHFKeychainUtils
Check for nil before creating featuredImageURL
Updating debug provisioning profile to newest version
Updating debug provisioning profile to newest version

Added Aaron's iPhone 4.