[memoize] Migrate to TypeScript

[sarayourfriend]

What:

Migrates the memoize package to TypeScript. This is a simple migration really. The main difference from the flow types was just needing to declare a name for the callback function's argument.

Why:

Part of #2358

How:

I renamed the index.js file to index.ts and then uncommented the Flow types and then updated them to TypeScript.

Checklist:

• Documentation N/A
• Tests N/A
• Code complete
• Changeset

I think the best way to test this is by running yarn build memoize and then verifying that the dist/declarations/src/index.d.ts file is correct.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1fe749f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 6 packages

Name	Type
@emotion/memoize	Minor
@emotion/babel-plugin	Patch
@emotion/cache	Patch
@emotion/css-prettifier	Patch
@emotion/is-prop-valid	Patch
@emotion/serialize	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 1fe749f:

Sandbox	Source
Emotion	Configuration

[sarayourfriend]

I think I may have messed up the changeset 😞 Is a changeset necessary for each individual migration PR or will we just have a single changeset when the ts-migration branch is merged? @Andarist

[Andarist]

I think I may have messed up the changeset 😞 Is a changeset necessary for each individual migration PR or will we just have a single changeset when the ts-migration branch is merged? @Andarist

Probably best to create a changeset per individual migration PR - you deserve the attribution in the generated (based on those changesets) changelog! 😉