Reader: update list stream paging

[eoigal]

Fixes https://github.com/Automattic/loop/issues/184

This PR works with the patch D163263-code. The patch adds an API handler for https://public-api.wordpress.com/rest/v1.3/read/list/automattic/a12s/posts API call from this PR.

The paging on the list posts page doesn't work well. This has to do with how the API handler for version 1.2 mishandles pagination on large lists like /read/list/automattic/a12s.

If you scroll down far enough on https://wordpress.com/read/list/automattic/a12s you probably will see the stream only load past couple of months of posts.

Now you should be able to keep streaming posts as you scroll down.

Before

list-posts-live-480.mov

After

streambuilder-480.mov

Proposed Changes

• Updates the /read/list Reader stream API call to include a page_handle and to use API version 1.3.

Why are these changes being made?

• Improve UX

Testing Instructions

• Make sure public-api.wordpress.com is sandboxed
• Go to /read/list/automattic/a12s and confirm the stream loads as expected in chronological order
• Go to /read/list/kristastevens/favorite-magazines and confirm the stream loads as expected in chronological order

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-121594

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-121594&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-121594&env=a8c-for-agencies

[matticbot]

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

Sections (~58 bytes added 📈 [gzipped])

name                             parsed_size           gzip_size
reader                                 +71 B  (+0.0%)      +58 B  (+0.0%)
plugins                                +71 B  (+0.0%)      +58 B  (+0.0%)
jetpack-cloud-plugin-management        +71 B  (+0.0%)      +58 B  (+0.0%)
home                                   +71 B  (+0.0%)      +58 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.

[eoigal]

The following patches have been deployed to add support for the list posts stream using Stream builder framework of the v1.3 API endpoint.

• D163263-code
• D163845-code
• D163853-code
• D163855-code
• D163943-code
• D163957-code
• D163970-code

[DustyReagan]

I tested this against the production API. I tested /read/list/kristastevens/favorite-magazines and /read/list/automattic/a12s.
✅ The posts are in reverse chronological order
✅ I can page/scroll much further back in time

[holdercp]

• I was able to scroll back months at /read/list/automattic/a12s without hitting an "end"
• The posts at /read/list/kristastevens/favorite-magazines were in reverse chronological order (most recent first)

I did repeatedly get a "Could not retrieve comments for post" error but I don't suspect that it's related to these changes. I did sandbox the API with trunk checked out.