fix: correct poetry lock command syntax

POETRY LOCK COMMAND FIX: Remove invalid --no-update option

Issue Fixed:
❌ The option "--no-update" does not exist
❌ poetry lock --no-update failing with invalid option

Root Cause:
- --no-update option doesn't exist in poetry lock command
- Incorrect command syntax causing poetry lock to fail

Solution Applied:
✅ Changed poetry lock --no-update to poetry lock
✅ Uses correct poetry lock command syntax
✅ Still regenerates lock file when needed
✅ Follows poetry documentation properly

Impact:
- Security scanning workflow now works correctly
- Poetry lock file regeneration succeeds
- Dependencies install properly after lock sync
- No more invalid option errors

This resolves the poetry command syntax issue that was
preventing the security scanning workflow from handling
out-of-sync poetry.lock files correctly.

.gitea/workflows/security-scanning.yml

@@ -92,7 +92,7 @@ jobs:
               $POETRY_CMD install --no-root
             else
               echo "poetry.lock is out of sync, regenerating..."
-              $POETRY_CMD lock --no-update
+              $POETRY_CMD lock
               echo "Installing dependencies with updated lock file..."
               $POETRY_CMD install --no-root
             fi