Upgrade psutil to 5.9.0

[mx-psi]

What does this PR do?

Upgrade psutil to 5.9.0. Validate builds are failing because of the need for DataDog/datadog-agent#10544.

Motivation

Include giampaolo/psutil#1961 fix

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• PR title must be written as a CHANGELOG entry (see why)
• Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
• PR must have changelog/ and integration/ labels attached

[mx-psi]

Windows E2E tests are failing with

ERROR: Could not install packages due to an EnvironmentError: [Error 5] Access is denied: u'c:\\program files\\datadog\\datadog agent\\embedded2\\lib\\site-packages\\~sutil\\_psutil_windows.pyd'

which seems like a CI issue?

[vickenty]

\\~sutil\\ bit looks fishy, a bad wheel perhaps?

[mx-psi]

Windows E2E tests are failing with

ERROR: Could not install packages due to an EnvironmentError: [Error 5] Access is denied: u'c:\\program files\\datadog\\datadog agent\\embedded2\\lib\\site-packages\\~sutil\\_psutil_windows.pyd'

which seems like a CI issue?

I can reproduce if I try to do python.exe -m pip install psutil==5.9.0 on the embedded Python 2 environment with the latest RC. psutil 5.9.0 seems to be detected as installed even if the failure happens.

The error does not happen if I try to install version 5.8.0, and after doing that it seems like I can upgrade to 5.9.0 seamlessly, even if I do 5.7.2 -> 5.8.0 -> 5.7.2 -> 5.9.0.

[mx-psi]

I am also able to reproduce it when installing on the embedded Python 2 environment of the Agent from DataDog/datadog-agent#10544 (i.e. using this msi) with the same behavior, so the custom patches are not the issue.

I can't reproduce with a fresh install of Python 2 when doing

C:\Python27\python.exe -m pip install psutil==5.7.2
C:\Python27\python.exe -m pip install psutil==5.9.0

[mx-psi]

I have restored this branch to its original setup and moved testing to #11196. To summarize: the end to end test failure is a limitation of the end to end testing environment, where the dependencies are updated while the Agent is running, and therefore holding some files.