Add some recommendations about how to install Poetry into an CI environment.

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

The example: https://python-poetry.org/docs/plugins/#application-plugins

Creates a `cleo.commands.command` from the factory, which is not compatible with the type `poetry.console.commands.command`. Use the correct type instead.

If a dependency doesn't specify a source type, then a locked package
from any source can satisfy it

The current "Managing Dependencies" documentation contains an error at
[Installing group dependencies](https://python-poetry.org/docs/managing-dependencies/#installing-group-dependencies)

Within the warning concerning the combined use of  `--with` and `--without` the parameters were swapped.

- [ ] Added **tests** for changed code.
- [x] Updated **documentation**

Co-authored-by: Philipp Quenzel <quenzel@dkms-lab.de>
Co-authored-by: finswimmer <finswimmer77@gmail.com>

*- ci: use 3.10 in release workflow
- ci: add 3.11 to the Python matrix

B023:  Functions defined inside a loop must not use variables redefined in the loop, because late-binding closures are a classic gotcha.

Here's some sample code approximating the poetry code:
```python
#!/usr/bin/env python3


def one() -> int:
    return 1


def two() -> int:
    return 2


def three() -> int:
    return 3


factories = [one, two, three]

registered = []
for factory in factories:
    registered.append(lambda: factory())

for registered_factory in registered:
    print(f"result is {registered_factory()}")
```
output is
```
result is 3
result is 3
result is 3
```
which is exactly the gotcha that flake8-bugbear's B023 was trying to warn about.

I've applied one of the workarounds that various parts of the internet recommend, and you can verify for yourself if you're so inclined that doing the same in the toy script gives the expected output.

refactor(provider): remove unused parameter "env" (environment must always be set via contextmanager "use_environment" to avoid inconsistent python_constraint)

refactor(solver): remove unnecessary parameter "provider" (was only used in tests and can cause inconsistencies between a solver and its provider)

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

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

eg with this dependency
```
pyscf = { git = "https://github.com/pyscf/pyscf", tag = "v2.0.1"}
```
the cloning of submodules fails - because that project has messed up and not committed the file saying what revision they want of the `doc` submodule.

Legacy git client just silently carries on, so I've done the same here.

- regular depth-first search already handles circular dependencies and
  hitting the same package twice
  - the special cases might have saved a teensy amount of work, but the
    simplification is preferable

- pre-release handling here was not consistent with code elsewhere, and
  since "elsewhere" happens first, it wins
  - given a constraint like ">=1.0" the removed code would have allowed
    1.0rc1, but elsewhere in the codebase constraints are taken to mean
    what they say

No functional change or fixes here, just tidier code:
* prefer Path.exists()
* typechecking - NormalizedNames from poetry-core
* clean up some unnecessary duplication
* minor refactor
* gather the pyproject.toml parsing into one block, save a level of indentation
* remove more dead code
* simplify handling of extras at command line
* more abstract types 

# Pull Request Check List

- [ ] Added **tests** for changed code.
- [ ] Updated **documentation** for changed code.

Bunch of improvements over `Configuration` documentation:
- Better show default value of options
- Add some missing `Introduced in <VERSION>` notes
- Add backticks around types for better readability

Will backport to `1.2` branch before final release.

test(installer): use locked version of vcs dependency without reference (branch, tag, rev) instead of latest

Requires: python-poetry/poetry-core#449

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