chore: fix all react/no-deprecated and react/prop-type eslint warnings

[kieckhafer]

Resolves #5247 & #5271
Impact: minor
Type: chore

Issue

We currently have many react/no-deprecated and react/prop-type eslint warnings.

Solution

Fix (or disable) these warnings, and then update our eslint rules to make react/no-deprecated and react/prop-type an error so new violations are not introduced.

I have update the components to use the UNSAFE_ version fo deprecated react life cycle methods, as these components will be updated to be functional components in the future.

Updated rules: reactioncommerce/reaction-eslint-config#15

Breaking changes

None.

Testing

1. run eslint
2. see there are no longer any react/no-deprecated and react/prop-type warnings (and no errors)

[kieckhafer]

@machikoyasuda not sure what the deal is with the DCO issue - it involves Maria's commits that aren't even in this branch. I've filed a ticket with them to see if they know what's going on: dcoapp/app#115

[machikoyasuda]

@kieckhafer You have 2 commits incorrectly signed off. To fix, head to your local branch and run:

git rebase HEAD~72 --signoff

Now your commits will have your sign off. Next run

git push --force-with-lease origin chore-kieckhafer-esling-reactNoDeprecated

[kieckhafer]

@machikoyasuda but those aren't my commits, and they aren't in this branch at all. They are commits from Maria... somewhere in the app.

[kieckhafer]

Fixed... somehow. It just went away when I made a new commit. Doesn’t make any sense to me, hopefully the ticket I made in that repo can provide some answers.