Update to handle Poetry 2.x

[loneil]

Steps to reproduce

1. Start from fresh (no existing image)
2. Have the dockerfile in oidc-controller just have RUN pip3 install --no-cache-dir poetry as the poetry install step (remove any version number, this has been fixed in main so the problem won't occur)
3. in docker run ./manage build

There was a major version release of Poetry that started causing a build issue in VCAuthN. Fixed this by setting a specific poetry version in the dockerfile (which we should do anyways).

The error Poetry version 2 is throwing on build (during poetry install step)

4.878 Installing the current project: acapy-vc-authn-oidc (0.2.2)
4.880
4.880 Warning: The current project could not be installed: No file/folder found for package acapy-vc-authn-oidc
4.880 If you do not want to install the current project use --no-root.
4.880 If you want to use Poetry only for dependency management but not for packaging, you can disable package mode by setting package-mode = false in your pyproject.toml file.
4.880 If you did intend to install the current project, you may need to set `packages` in your pyproject.toml file.
4.880
------
Dockerfile:9
--------------------
   7 |
   8 |     COPY pyproject.toml poetry.lock README.md ./
   9 | >>> RUN poetry install --only main
  10 |
  11 |     COPY ./oidc-controller .
--------------------
ERROR: failed to solve: process "/bin/sh -c poetry install --only main" did not complete successfully: exit code: 1

Fix above (likely a directory naming issue? In the dockerfile root? Or don't need to package up?)

Also check poetry docs to see if there's any improvements or other fixes needed
https://python-poetry.org/blog/announcing-poetry-2.0.0/

[esune]

I think we could add the package definition (see acapy as an example) if it fixes the problem. This would make it possible to create/distribute a package artifact in the future if we wanted to. That being said, i don;t think that skipping packaging would be a big issue/drawback if it comes down to that.