Use the version from poetry.core always, one implementation is enough

Co-authored-by: Bjorn Neergaard <bjorn@neersighted.com>

Testing against newer versions will help us keep abreast of any upcoming
issues. The older versions can be added as partial matrix entries if
desirable, but I do not believe this to be necessary.

Also re-order mypy in the workflow so that type errors fail fast (before
tests are run).

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

Co-authored-by: Bjorn Neergaard <bjorn@neersighted.com>

perf(solver): reduce the number of overrides by avoiding adding dummy dependencies if the project's python constraint does not allow any version compatible with the marker of the dependency

Co-authored-by: Bjorn Neergaard <bjorn@neersighted.com>

This change ensures that when http repositories inspect package
metadata from py2 and py3 wheels, python version requirements are
merged. Without this change, in cases where these wheels have different
python constraints, attempting to lock these packages will lead to
solver errors.

Resolves: #5074

This change replaces the `--no-binary` option introduced in #5600 as
the original implementation could cause inconsistent results when the
add, update or lock commands were used.

This implementation makes use of a new configuration
`installer.no-binary` to allow for user specification of sdist
preference for select packages.

With this change, Poetry now creates an ephemeral build environment
with all requirements specified under `build-system.requires` when a
build script is specified. Otherwise, project environment is reused.

Prior to this change when Poetry builds a project with a setup.py file,
as in the case when `generate-setup-file` was set to true, `pip`
fallback was invoked with a PEP 517 isolated build causing it to fail.

This was a regression in functionality from Poetry 1.1 build script
usage. However, note that build script usage is an experimental
feature.