read package name from pypi info .info.name
close #2098

Resolves: #2333

Prior to this change, when checking solver results the tests cases
relied on the weaker equality check of the `Package` class. With
python-poetry/poetry-core#53, the check has been made stricter.

This change, while having no functional impact, ensures that once
poetry-core is updated, tests do not fail unexpectedly.

This works around a glob parsing bug in cirrus-ci.

Relates-to: cirruslabs/cirrus-ci-docs#696

Relax tomlkit version requirement

Co-authored-by: Arun Babu Neelicattu <arun.neelicattu@gmail.com>

Improve detection of installed packages in an environment

* ci: artifact release automation for freebsd

Resolves: #2309

* ci: limit python versions to 2.7 and 3.7 (freebsd)

* ci: ignore action checks for cirrus only change

A package installed from git is sometimes mistaken as a standard
package since it has a `.dist-info` directory. This change ensures
that the pth file sources are also taken into consideration when
determining if a package is git sourced.

Additionally, this change ensures that a pth file is searched for in
both platlib and purelib site directories.

When detecting installed packages, ensure that we check both purelib
and platlib site directories when determining if a package is a
standard package.

Cached artifact uri was previously constructed manually using a string
representation of the artifact path. This change ensures that the uri 
is generated by pathlib instead.

Resolves: #2744

Co-authored-by: Fredrik Averpil <fredrik.averpil@ericsson.com>
Co-authored-by: Arun Babu Neelicattu <arun.neelicattu@gmail.com>

This change ensures that non fancy io can use parallel installs.

Release 1.1.0b2

Release 1.1.0b1

Display logging messages from poetry-core when building

This change replaces setup.py explicit execution in favour of pep517
metadata builds.

In addition to improving handling of PEP 517 metadata builds, error
handling when reading setup files have also been improved.

This ensures to use the correct python executable.
Using `run` simply uses `sys.prefix` with a bin suffix, which is not necessarily the currently used python executable.

E.g. when linking a specific python version to a custom directory, using `sys.prefix` may point to the wrong python version:
* /usr/bin/python2.7
* /usr/bin/python3.6
* /usr/bin/python is a symlink to 2.7
* /usr/bin/local/python (or any other location) is a symlink to 3.6 which shadows the former symlink
`sys.prefix` is `/usr` in this case, which is correct, but the `python` executable there points to the wrong version.

`run_pip` in the env fixes this already by using `sys.executable`, see https://github.com/python-poetry/poetry/blob/develop/poetry/utils/env.py#L964
This should be used in the executor as well.

Co-authored-by: Jonathan Striebel <jstriebel@users.noreply.github.com>