Use Ruby 1.9 hash syntax in Podfile suggestion comments

[mokagio]

This should avoid noisy lint errors such as this
#19807 (comment)

The method I used to make these changes was to uncomment all the suggestions, run RuboCop with -A, and recomment.

Testing

This PR only touches comments. So there's nothing to test.

Regression Notes

1. Potential unintended areas of impact – N.A.
2. What I did to test those areas of impact (or what existing automated tests I relied on) – N.A.
3. What automated tests I added (or what prevented me from doing so) – N.A.

---

• I have completed the Regression Notes.
• I have considered adding unit tests for my changes. N.A.
• I have considered adding accessibility improvements for my changes. N.A.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary. N.A.

[mokagio]

Actually, we should delete this because it adds little to what we can already do with the standard syntax.

I suppose it might have been useful in the past, before we had our own specs source repository.

[mokagio]

Suggested change

# pod 'WPMediaPicker', git: 'https://github.com/wordpress-mobile/MediaPicker-iOS.git', tag: '1.7.0'

[wpmobilebot]

You can test the changes in Jetpack from this Pull Request by:

• Clicking here or scanning the QR code below to access App Center
• Then installing the build number pr19963-880311f on your iPhone

If you need access to App Center, please ask a maintainer to add you.

[wpmobilebot]

You can test the changes in WordPress from this Pull Request by:

• Clicking here or scanning the QR code below to access App Center
• Then installing the build number pr19963-880311f on your iPhone

If you need access to App Center, please ask a maintainer to add you.