Reader: fix /following route

[bluefuton]

Changes proposed in this Pull Request

While working on some routing changes (D45105-code) I noticed that Calypso doesn't handle the /following route but it does handle /following/manage and /following/edit.

Working on the principle that good URLs should be hackable, and therefore that some users will end up at /following even though we're not linking to it anywhere, this PR adds a redirect to /read from that route.

Testing instructions

• Visit http://calypso.localhost:3000/following and ensure that you're redirected to /read.
• Visit http://calypso.localhost:3000/following/manage and ensure that you still reach Manage Following.

[matticbot]

Test live: https://calypso.live/?branch=add/reader-following-route-redirect

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~4 bytes added 📈 [gzipped])

name    parsed_size           gzip_size
reader        +26 B  (+0.0%)       +4 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[jsnmoon]

👍 Works as described.