2018.3.0 release details (microsoft#1227)

Cherry-pick Pipfile detection fix for 2018.2.1 (microsoft#1002)

* Detect pipenv by looking for Pipfile, not pipfile (microsoft#994)

On platforms with case-sensitive filesystems, like Linux, these are not
equivalent. pipenv documents that the file should be called Pipfile[0]
and `Pipfile.find()` only finds files matching this exact case[1].

As a result, even if `pipenv --venv` in `cwd` would return success, it
will never be run on Linux, and Code never detects the pipenv. (You can
work around this with `touch pipfile`.) With this change, it's detected
successfully. I believe there's no need to add a backwards-compatibility
check for the old case, because on platforms where the old, incorrect
check worked, so will the new, correct one.

[0] https://docs.pipenv.org/basics/#example-pipfile-pipfile-lock
[1] https://github.com/pypa/pipfile/blob/5acb9ac7/pipfile/api.py#L76-L85

* Prep for 2018.2.1

Prep for the February release (microsoft#968)

* Bump the version to 2018.2.0
* Update the changelog

Prep for 2018.1 final (microsoft#683)

* Bump version number to final

* Add release date

* Mention the cached interpreter change

Merge branch 'master' into Release-0.9.1

Merge remote-tracking branch 'upstream/master'

* upstream/master:
  Update the TPN (microsoft#415)
  0.9.0 release details (microsoft#407)

0.8.0 release

new version

new version

updated version for new build