Update vendored dependencies, relevant API usage, and CI config

[techalchemy]

Update vendored dependencies and invocations

• Update vendored and patched dependencies
  • Update patches on piptools, pip, pip-shims, tomlkit
• Fix invocations of dependencies
  • Fix custom InstallCommand instantiation
  • Update PackageFinder usage
  • Fix Bool stringify attempts from tomlkit

Updated vendored dependencies:

• attrs: 18.2.0 => 19.1.0

• certifi: 2018.10.15 => 2019.3.9

• cached_property: 1.4.3 => 1.5.1

• cerberus: 1.2.0 => 1.3.1

• click: 7.0.0 => 7.1.1

• click-completion: 0.5.0 => 0.5.1

• colorama: 0.3.9 => 0.4.3

• contextlib2: (new) => 0.6.0.post1

• distlib: 0.2.8 => 0.2.9

• funcsigs: (new) => 1.0.2

• importlib_metadata 1.3.0 => 1.5.1

• importlib-resources: (new) => 1.4.0

• idna: 2.7 => 2.9

• jinja2: 2.10.0 => 2.11.1

• markupsafe: 1.0 => 1.1.1

• more-itertools: (new) => 5.0.0

• orderedmultidict: (new) => 1.0

• packaging: 18.0 => 19.0

• parse: 1.9.0 => 1.15.0

• pathlib2: 2.3.2 => 2.3.3

• pep517: (new) => 0.5.0

• pexpect: 4.6.0 => 4.8.0

• pip-shims: 0.2.0 => 0.5.1

• pipdeptree: 0.13.0 => 0.13.2

• pyparsing: 2.2.2 => 2.4.6

• python-dotenv: 0.9.1 => 0.10.2

• pythonfinder: 1.1.10 => 1.2.2

• pytoml: (new) => 0.1.20

• requests: 2.20.1 => 2.23.0

• requirementslib: 1.3.3 => 1.5.4

• scandir: 1.9.0 => 1.10.0

• shellingham: 1.2.7 => 1.3.2

• six: 1.11.0 => 1.14.0

• tomlkit: 0.5.2 => 0.5.11

• urllib3: 1.24 => 1.25.8

• vistir: 0.3.0 => 0.5.0

• yaspin: 0.14.0 => 0.14.3

• zipp: 0.6.0

• Removed vendored dependency cursor.

[brainwane]

btw @davidstaheli do you have any time to help us wrangle Azure pipelines? We're having a problem here https://dev.azure.com/pypa/pipenv/_build/results?buildId=21032&view=logs&j=89390fe7-33d2-53e5-d9b1-9b3b600e8bb2&t=154e6688-01f7-599c-c8c6-29bc92fc1d2f where it's unclear whether the "Run integration tests" step is kicking off at all.

[brainwane]

Fun fact: Azure jobs time out and sometimes that is confusing.

According to the past-180-days failure report pipenv's builds started failing between 2020-01-10 and 2020-01-12 -- we can't see those builds because they are over 30 days old, but we suspect that, at some point there, some runs went over the 60 minute mark and thus things started failing (example).

So this PR is still in progress as Dan splits up the tests so each one takes under 60 minutes, because that sounds faster than fiddling with the timeout variable and talking to Microsoft support to remind them that -- as a public open source project -- pipenv should get much longer timeouts. (IRC log.) If you want to help, you can join us in IRC, #pypa-dev on Freenode, or comment here with tips.

[brainwane]

I just spoke with Dan. Turns out the Windows problem that stymied him for a while was host key validation, which he has now fixed, so Windows tests are now running and actually reporting failures. The current failures require that he normalize capitalization of the directories/files in the test environments, and so do not seem to reflect any actual bugs in pipenv functionality. So that's good news!

Mac and Linux tests are evidently passing. So once he gets those Windows tests passing, he should be able to merge the branch and get that prerelease out (#3369).

[brainwane]

From IRC in the past few days:

windows failures don't appear in azure test results
the builds fail but nothing indicates what went wrong
https://dev.azure.com/pypa/pipenv/_build/results?buildId=21643&view=results why doesn't windows report its failures :|
it fails but reports nothing

Dan has tried runing a subset of the tests in the CI and that didn't help. Azure and Windows testing experts: please help.

[pietrodn]

If you click on "Run integration tests" it is impossible to get to the actual test report. However if you click on the name of the test environment, such as "TestWindows Python38", you are shown a link such as "93,6% tests passed" on the right: if you click on it, you get the actual outcome of the tests.

I'll include an image to be more clear.

Here's the failure: log, code

[brainwane]

@pradyunsg also started poking at this problem in a branch. I don't think he has a lot of time to submit pull requests about it; I link to it in case it serves as a basis and helps anyone else submit pipenv PRs or recommend things for Dan to do in this PR.