run npx react-codemod rename-unsafe-lifecycles on javascript files

[ryanfiller]

This PR is to address the following console warnings in version 21.8.0

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: CalendarMonth, CalendarMonthGrid, DayPicker, DayPickerKeyboardShortcuts, DayPickerRangeController react-dom.development.js:91

Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

* Move data fetching code or side effects to componentDidUpdate.
* Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: DayPicker react-dom.development.js:91

npx react-codemod rename-unsafe-lifecycles was run with the javascript option.

[ljharb]

This is very much not desired, and would be a breaking change since we'd have to drop support for React older than v16.3.

[ljharb]

See #1748.