ReplyEditor revamp

[roadscape]

ReplyEditor is one of the most complex components in the repo, and contains the most debt. Modifications without unintended side effects are difficult. This issue will be updated with more notes and strategies.

• ReplyEditor prop usage to be documented and cleaned (remove {...comment})
• When editing a post, ReplyEditor should fetch (raw) getContent to base json_metadata
  • (will allow trimming of API responses where only data use is to pass to Editor)
• Component logic to be untangled (isStory, isEdit, comment as obj to edit vs. reply to; category as tags vs. primary vs. field name)