fix: remove invalid --no-update flag from poetry lock command

POETRY LOCK COMMAND FIX: Use correct poetry lock syntax

Issue:
- The option --no-update does not exist for poetry lock
- Poetry lock command failing due to invalid flag
- Dependencies not being installed properly

Solution:
- Remove --no-update flag from poetry lock command
- Use 'poetry lock' without additional flags
- Maintain error handling for lock file update
- Applied to both test jobs

Expected results:
- Poetry lock should succeed with correct syntax
- Dependencies should install properly
- Test workflow should proceed to execution
- No more poetry command errors

This fixes the poetry command syntax error while maintaining
the lock file update functionality.

.gitea/workflows/python-tests.yml

@@ -89,7 +89,7 @@ jobs:
             # Install dependencies only (skip current project to avoid package issues)
             echo "Installing dependencies with poetry (no-root mode)..."
             # Update lock file if pyproject.toml changed
-            $POETRY_CMD lock --no-update || echo "Lock file update completed"
+            $POETRY_CMD lock || echo "Lock file update completed"
             $POETRY_CMD install --no-root
             
             echo "=== ADDITIONAL DEPENDENCIES ==="
@@ -233,7 +233,7 @@ jobs:
             [ -f "$POETRY_CMD" ] && POETRY_CMD="$POETRY_CMD" || POETRY_CMD="poetry"
             
             python3 -m venv venv && source venv/bin/activate
-            $POETRY_CMD lock --no-update || echo "Lock file update completed"
+            $POETRY_CMD lock || echo "Lock file update completed"
             $POETRY_CMD install --no-root
             venv/bin/pip install pydantic-settings sqlmodel sqlalchemy requests slowapi pytest pytest-cov pytest-mock