fix(react): Add explicit dependency on csstype for v16

[eps1lon]

Closes #49713

I forgot to move the package.json when creating v16 types in #48971.

Please fill in this template.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change.
• Follow the advice from the readme.
• Avoid common mistakes.
• Run npm test <package to test>.

Select one of these and delete the others:

If changing an existing definition:

• [ ] Provide a URL to documentation or source code which provides context for the suggested changes
• [ ] If this PR brings the type definitions up to date with a new version of the JS library, update the version number in the header.
• [ ] If you are making substantial changes, consider adding a tslint.json containing { "extends": "dtslint/dt.json" }. If for reason the any rule need to be disabled, disable it for that line using // tslint:disable-next-line [ruleName] and not for whole package so that the need for disabling can be reviewed.

[typescript-bot]

@eps1lon Thank you for submitting this PR!

This is a live comment which I will keep updated.

This PR doesn't modify any tests, so it's hard to know what's being fixed, and your changes might regress in the future. Have you considered adding tests to cover the change you're making? Including tests allows this PR to be merged by yourself and the owners of this module. This can potentially save days of time for you.

1 package in this PR

• react on npm, on unpkg (author is owner)
  • owner-approval: @ferdaber

Code Reviews

Because this is a widely-used package, a DT maintainer will need to review it before it can be merged.

Status

• ✅ No merge conflicts
• ✅ Continuous integration tests have passed
• ❌ Only a DT maintainer can approve changes without tests

Once every item on this list is checked, I'll ask you for permission to merge and publish the changes.

---

Diagnostic Information: What the bot saw about this PR

{
  "type": "info",
  "now": "-",
  "pr_number": 49717,
  "author": "eps1lon",
  "headCommitAbbrOid": "0ed44b4",
  "headCommitOid": "0ed44b4ec50455bc83b6d5110b5bc151fc98034a",
  "stalenessInDays": 0,
  "lastPushDate": "2020-11-21T15:16:04.000Z",
  "lastCommentDate": "2020-11-21T16:18:32.000Z",
  "maintainerBlessed": false,
  "hasMergeConflict": false,
  "isFirstContribution": false,
  "popularityLevel": "Critical",
  "pkgInfo": [
    {
      "name": "react",
      "kind": "edit",
      "files": [
        {
          "path": "types/react/v16/package.json",
          "kind": "package-meta-ok"
        }
      ],
      "owners": [
        "johnnyreilly",
        "bbenezech",
        "pzavolinsky",
        "digiguru",
        "ericanderson",
        "DovydasNavickas",
        "theruther4d",
        "guilhermehubner",
        "ferdaber",
        "jrakotoharisoa",
        "pascaloliv",
        "hotell",
        "franklixuefei",
        "Jessidhia",
        "saranshkataria",
        "lukyth",
        "eps1lon",
        "zieka",
        "dancerphil",
        "dimitropoulos",
        "disjukr",
        "vhfmag",
        "hellatan"
      ],
      "addedOwners": [],
      "deletedOwners": [],
      "popularityLevel": "Critical"
    }
  ],
  "reviews": [
    {
      "type": "approved",
      "reviewer": "ferdaber",
      "date": "2020-11-21T19:29:46.000Z",
      "isMaintainer": false
    }
  ],
  "ciResult": "pass"
}

[typescript-bot]

🔔 @johnnyreilly @bbenezech @pzavolinsky @digiguru @ericanderson @DovydasNavickas @theruther4d @guilhermehubner @ferdaber @jrakotoharisoa @pascaloliv @Hotell @franklixuefei @Jessidhia @saranshkataria @lukyth @zieka @dancerphil @dimitropoulos @disjukr @vhfmag @hellatan — please review this PR in the next few days. Be sure to explicitly select Approve or Request Changes in the GitHub UI so I know what's going on.

[ferdaber]

Should the semver constraint be more lax to prevent accidental duplication?

[eps1lon]

Should the semver constraint be more lax to prevent accidental duplication?

Just copied it from the current typings. I don't know if we're compatible with other major versions.

[typescript-bot]

👋 Hi there! I’ve run some quick measurements against master and your PR. These metrics should help the humans reviewing this PR gauge whether it might negatively affect compile times or editor responsiveness for users who install these typings.

Let’s review the numbers, shall we?

Comparison details 📊

	master	#49717	diff
Batch compilation
Memory usage (MiB)	130.8	127.4	-2.6%
Type count	34897	34897	0%
Assignability cache size	8284	8284	0%
Language service
Samples taken	2860	2860	0%
Identifiers in tests	2941	2941	0%
getCompletionsAtPosition
Mean duration (ms)	256.7	255.8	-0.3%
Mean CV	8.4%	8.5%
Worst duration (ms)	1115.3	1078.0	-3.3%
Worst identifier	props	x
getQuickInfoAtPosition
Mean duration (ms)	255.8	254.5	-0.5%
Mean CV	8.7%	8.5%
Worst duration (ms)	887.2	781.5	-11.9%
Worst identifier	x	ref

It looks like nothing changed too much. I won’t post performance data again unless it gets worse.

[typescript-bot]

I just published @types/react@16.14.2 to npm.