Fix Poetry v2.0.0 compatibility (#9197)

Make all changes necessary to make everything work with Poetry v2.0.0.

- Resolves #9196

## Changes
- Removed `--no-update` flag from `poetry lock` command in codebase
- Removed extra path arguments from `poetry -C [path] run [command]`
occurrences
- Regenerated all lock files in hierarchical order
- Added workaround for Poetry bug where `packages.[i].format` is now
suddenly required

Additionally:
- Fixed up .dockerignore
  - Fixes .venv being erroneously copied over from local
  - Fixes build context bloat (300MB -> 2.5MB)
- Fixed warnings about entrypoint script not being installed in docker
builds

### Relevant (breaking) changes in v2.0.0
- `--no-update` flag no longer exists for `poetry lock` as it has become
default behavior
- The `-C` option now actually changes the directory, so any path
arguments in `poetry run` commands can/must be removed
- Poetry v2.0.0 uses the new v2.1 lock file spec, so all lock files have
to be regenerated to avoid false-positive lock file updates and checks
on future PRs
- **BUG:** when specifying `poetry.tool.packages`, `format` is required
now
  - python-poetry/poetry#9961

Full Poetry v2.0.0 release notes and change log:
https://python-poetry.org/blog/announcing-poetry-2.0.0

.github/workflows/platform-backend-ci.yml

@@ -81,7 +81,7 @@ jobs:
 
       - name: Check poetry.lock
         run: |
-          poetry lock --no-update
+          poetry lock
 
           if ! git diff --quiet poetry.lock; then
             echo "Error: poetry.lock not up to date."

.github/workflows/platform-frontend-ci.yml

@@ -88,6 +88,11 @@ jobs:
         run: |
           yarn test --project=${{ matrix.browser }}
 
+      - name: Print Docker Compose logs in debug mode
+        if: runner.debug
+        run: |
+          docker compose -f ../docker-compose.yml logs
+
       - uses: actions/upload-artifact@v4
         if: ${{ !cancelled() }}
         with: