Update README.md "Updating Poetry"

Currently the note in "Updating Poetry" is different from the one below in "Enable tab completion for Bash, Fish, or Zsh". This MR is to make them more consistent.

Fix non-compliant Git URL matching

RFC 3986 § 2.3 permits more characters in a URL than were matched. This
corrects that, though there may be other deficiencies. This was a
regression from v1.0.2, where at least “.” was matched without error.

* fix downloading packages from simplepypi

* unused code removed

* remove unused imports

# Conflicts:
#	poetry/utils/password_manager.py

The previous regexp was only taking the first integer of the version number,
this presented problems when the major version number reached double digits.

Poetry would determine that the version of the dependency is '1', rather than,
ie: '14'. This caused failures to solve versions.

* fix (git): match for `\w` instead of `.` for getting user

* change (vcs.git): hold pattern of the regex parts in a dictionary to be consistent over all regexs

* new (vcs.git): test for `parse_url` and some fixes for the regex pattern

* new (vcs.git): test for `parse_url` with string that should fail

* fix (test.vcs.git): make flake8 happy

fix (masonry.api): `get_requires_for_build_wheel` must return additional list of requirements for building a package, not listed in `pyproject.toml` and not dependencies for the package itself (#1875)

fix (tests): adopted tests

Documentation: Fix `build` command

Revert "create PEP508 compliant dependency string for directory and file dependencies (#1796)" (#1865)

This reverts commit 10e471a0.

* fix (directory_dependency, file_dependency): create PEP508 compliant dependency string for directory and file dependencies

* fix (directory_dependency, file_dependency): making isort and black happy

* change (env.py): force recreation of venv if it is not sane

* new (env): add warning when forcing recreation

* fix (env): warning about broken venv placed right before calling recreation

* Update poetry/utils/env.py

Co-Authored-By: Sébastien Eustace <sebastien.eustace@gmail.com>

Co-authored-by: Sébastien Eustace <sebastien.eustace@gmail.com>

* fix(exporter): don't export local file dependency as editable

* fix(exporter): don't check for source_type "url" when prepending `-e`

Update CONTRIBUTING.md

Update the contributing instructions to use python-poetry instead of sdispater as the repository namespace.

* Handle nested wildcards in package includes correctly. Fixes: #1379.

Use compat `Path`.

* Ensure that when building sdists, subpackages with Python files (but not necessarily an __init__.py file) will be included.

* fix: removed hint for uninstall poetry, after installation.

* change (get-poetry.py): changed hint about uninstalling poetry

* fix (get-poetry.py): typo

* Fix PEP440 compatible release (`~=`) handling

PEP440 compatible release version range (`~=`) should have itself as a minimum
value. Examples from [official
doc](https://python.org/dev/peps/pep-0440/#compatible-release) (each pair is
equivalent):

```
~=2.2
>=2.2, ==2.*

~=1.4.5
>=1.4.5, ==1.4.*

~=2.2.post3
>=2.2.post3, ==2.*

~=1.4.5a4
>=1.4.5a4, ==1.4.*
```

In every case, lower bound is exactly same as the input version. Current
incorrect behavior was originally introduced 2 years ago by commit c55d55a8,
where it tried to reset patch version to 0 for tilde expression.

Closes #1150.

* Fix Black lint

Expand documentation of `git` dependency subkeys

I need to pin a dependency to a specific git commit hash. After reading
these docs, it was not clear to me that I could do so with the `rev`
key, because "something else" is vague. I wound up digging into the
source code and learned what I needed there.

This change expands the documentation for `git` dependencies to explain
the sub-keys in more detail and give examples of how to use each.