* 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

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>

Merge develop into master

# Conflicts:
#	.github/workflows/release.yml
#	CHANGELOG.md
#	Makefile
#	make-linux-release.sh
#	poetry.lock
#	poetry/__version__.py
#	poetry/packages/locker.py
#	pyproject.toml
#	tests/packages/test_locker.py

Merge unreleased changes from master into develop

Release 1.0.10

Previously, the editable builder contained a regression that only
included poetry root when generating .pth files. This change ensure
that all package or module sources are included as per configuration.

Resolves: #2657

I think this should also fix the confusing syntax highlighting at https://python-poetry.org/docs/dependency-specification/#expanded-dependency-specification-syntax where the `platform_python_implementation == 'CPython'` string literal edited here is not currently highlighted as a literal string value.

This is a workaround for a bug in 1.0.9 causing a recursion error when
installing dependencies.

# Conflicts:
#	.github/workflows/main.yml
#	CHANGELOG.md
#	docs/docs/cli.md
#	get-poetry.py
#	poetry/packages/package.py
#	poetry/spdx/__init__.py
#	poetry/utils/env.py
#	poetry/vcs/git.py
#	tests/packages/test_package.py
#	tests/spdx/test_main.py
#	tests/utils/test_env.py

Until now poetry used the built-in venv module available in Python 3.
This has presented a few concerns. Chief of which has been
inconsistent environment setup. This includes, but is not limited to,
pip version used by the `ensurepip` module which is in turn used by the
built-in `venv.EnvBuilder`. Additionally, the `virtualenv` package
allows for faster environment creation. This can also allow us to, going
forward, drop ad-hoc code required to inspect and manage environments.