Comment replies using keyboard accessory

This replaces the 3 different comment replying experiences with a single experience provided by `InlineComposerView`

(See #612)

## General Strategy

In order to handle different keyboard modes (iPad docked vs split) and different keyboard sizes the commenting UI is implemented as a `[UIResponder inputAccessoryView]` and provides a delegate `InlineComposeViewDelegate` protocol to allow other components to handle user input.

![screen shot 2013-12-16 at 10 12 00 am](https://f.cloud.github.com/assets/19795/1757239/f6fd155a-667d-11e3-8ac4-003cc36bbe23.png)
_iPhone toolbar_

![screen shot 2013-12-16 at 10 14 00 am](https://f.cloud.github.com/assets/19795/1757246/0a8c8e3e-667e-11e3-8fec-b708efea1434.png)
_iPad split toolbar_

By default the `InlineComposeView` does not display any UI until it becomes the first responder and uses a hidden`UITextView` to activate the built in keyboard and assigns the `[UIResponder inputAccessoryView]` to display the toolbar above the keyboard. 

Additional benefits of using a `[UIResponder inputAccessorView]` is that the keyboard notification `userInfo` will include this view in it's frame calculations so `UITableViewController` will automatically update the `contentInset` for the controller's view. This means we no longer have to finagle the controller's views when the keyboard is displayed nor do we need to care where the keyboard is since it will always be attached to the keyboard.

__Reader__: `ReaderCommentPublisher` is a utility that replaces the networking portion of the `ReaderCommentFormView` and allows the `ReaderPostsViewController` and the `ReaderPostDetailViewController` to reuse the same delegate to reduce code duplication (fixes #754).

__Comment Notification__: The comment notification experience is pretty much the same other than using the new input method.

__Me/Blog/Comments__:`ReplyToCommentViewController` has been replaced with the `InlineComposeView`.