Framework: enable redux persistence on horizon and dev

[gwwar]

This PR turns on redux-persistence for horizon and development environments.

Before Merging:

• Framework: add approach for redux data persistence #3267 update our approach to data doc
• Framework: build redux store from scratch if persisted data is too old #3271 simple max age mechanism to throw out data
• Framework: add separate server state hydration #3343 separate server state hydration

State Tree Status

• application - never persisted
• current-user - persisted with schema checks
• notices - never persisted
• plugins - not persisted, needs schema PR
• post-types - persisted with schema checks
• posts - not persisted, in progress schema PR Framework: add schema for posts #3487
• receipts - not persisted, needs a schema PR
• sharing/publicize - not persisted, in progress schema PR Framework: add schema for sharing/publicize #3357
• site-settings/exporter - not persisted, needs a schema PR
• sites/plans - not persisted, schema PR blocked by Framework: redux sites contains functions #2757
• sites - not persisted, see: Framework: should sites be wrapped? #3624 Framework: redux sites contains functions #2757. Themes currently expects decorated sites decorated sites, and needs to be refactored.
• support - not persisted, needs a schema PR
• themes - not persisted, schema PR Framework: add schemas for themes state tree #3403
• ui - never persisted Framework: Refuse to persist any UI state #3337
• users - not persisted, needs a schema PR

cc @rralian

[mtias]

@gwwar any reason why enabling this for horizon and not wpcalypso?

[gwwar]

Ah thanks, I think I forgot to turn this on for wpcalypso. :)

[rralian]

@gwwar We should probably enable in staging as well. I think it gets more usage than horizon so we'll probably surface issues faster.

[mtias]

@gwwar heh, no worries :) I think in general it's good to have it in wpcalypso for a bit before hitting staging.