Update poetry.lock

[marcofavoritobi]

Proposed changes

This PR updates the poetry.lock file using the command poetry update.

Fixes

n/a

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply.

• I have read the CONTRIBUTING doc
• I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works

Further comments

n/a

[codecov-commenter]

Codecov Report

Merging #18 (c07b097) into main (8221916) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

❗ Current head c07b097 differs from pull request most recent head 027ae63. Consider uploading reports for the commit 027ae63 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
- Coverage   99.46%   99.44%   -0.02%     
==========================================
  Files          25       22       -3     
  Lines        1116     1086      -30     
==========================================
- Hits         1110     1080      -30     
  Misses          6        6              

Impacted Files	Coverage Δ
black_it/loss_functions/gsl_div.py	100.00% <100.00%> (ø)
black_it/plot/plot_results.py	100.00% <100.00%> (ø)
black_it/samplers/random_forest.py	100.00% <100.00%> (ø)
black_it/utils/__init__.py
black_it/__init__.py
black_it/utils/base.py

[marcofavoritobi]

docs dependencies have been pinned to exact versions since, as it often happened in the past, the "docs stack" is fragile wrt version updates.

[muxator]

LGTM.

• the intermediate commits expose slight pre-existing problems that are then fixed later in the series. In this case this is a good strategy, since the history does a very good job of explaining where the problems laid;
• the lockfile has been regenerated with Poetry 1.2.1. pyproject.toml does not use any 1.1-specific features, and thus the lockfile is compatible with older Poetry versions. Tested an installation with 1.1.15 and it works well;
• replicated locally the test suite, lint and static checks, and all looks good.

Merging, thanks.