Poetry fails with "No module named 'packaging.licenses'"

[KamilPacanek]

I have AzureDev Pipeline running poetry, the details looks like this:

  - bash: |
      cd PROJECT_DIR
      poetry config virtualenvs.create false
      poetry lock
      poetry install
    displayName: 'Poetry install'

  - bash: |
      cd PROJECT_DIR
      poetry export \
        -o requirements.txt \
        --without-hashes \
        --with "..."
      mv requirements.txt SOME_PATH
    displayName: 'Poetry export'

It works fine with v2.1.4 and starts to fail with v2.2.0 and v2.3.1 (latest) on the export step:

No module named 'packaging.licenses'
mv: cannot stat 'requirements.txt': No such file or directory

As you can see the poetry is configured to run without virtual environment (poetry config virtualenvs.create false). When I shell into the DevOps Agent that runs the pipeline I can see the python3.11 is installed yet the which command returns the old version.

That's said python3 -m pip show packaging returns some error about pip not being a module, and python3.11 -m pip show packaging returns information that v26.0 is installed (and required by poetry, among others).

I see in the changelog that version v2.2.0 bumped the requirement for packaging (#10413).

I suspect that the issue is somewhere along here - the python version conflict.
Any ideas?