Update reader conversations tests to typeScript

[Addison-Stavlo]

Related to # #101792 - in reviewing this @mehmoodak noted the opportunity to convert a couple of these files to typescript.

Proposed Changes

Updates a couple reader files to typescript.

Why are these changes being made?

• Ongoing effort to convert files to typescript to improve devex.

Testing Instructions

• smoke test
• ensure checks pass

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 UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• 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-138721

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

This PR does not affect the size of JS and CSS bundles shipped to the user's browser.

Generated by performance advisor bot at iscalypsofastyet.com.

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• blaze-dashboard
• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/reader-actions-to-typescript on your sandbox.

[mehmoodak]

Thanks for refactoring the code to TypeScript.

[mehmoodak]

Can we use this from

import { Dispatch } from 'redux';

[Addison-Stavlo]

That wouldn't be a mock function would it? That would just be the standard redux dispatch?

[mehmoodak]

You're right. VSCode doesn't give any error to me when I used it, maybe it was waiting on Intellisense.

[Addison-Stavlo]

Yeah, I feel like the more we use TS here the slower intellisense becomes. 😢

[mehmoodak]

Looking forward to TS go-compiler with 10x improvement 🤞

[Addison-Stavlo]

That would be awesome.

[mehmoodak]

Better if we can add an interface for the state. Not a blocker.

[Addison-Stavlo]

This was WSOD'ing the reader due to the init file not properly initializing the reader store after being converted to typescript. I tried a couple things that I thought would resolve the issue but I keep running into errors.

Im going to leave init.js the way it is. It doesn't seem very beneficial to change to typescript anyways.