fix: Pattern for package-lock.json match

Author: d3xter666

.github/workflows/release-please.yml

@@ -50,14 +50,17 @@ jobs:
           # to old versions (^4.0.x) which are still correct and should not be updated to new versions (^5.0.x)
           # that don't exist on npm yet. We restore these specific entries from the main branch.
           # Restore original entries for @ui5/*-npm packages to avoid unintended updates
-          git show origin/main:package-lock.json | jq -r '.packages | to_entries[] | select(.key | test("node_modules/@ui5/(builder|cli|fs|logger|project|server)-npm$")) | .key' | while read key; do
+          # Note: npm aliases can be in node_modules or internal/documentation/node_modules
+          git show origin/main:package-lock.json | jq -r '.packages | to_entries[] | select(.key | test("(node_modules|internal/documentation/node_modules)/@ui5/(builder|cli|fs|logger|project|server)-npm$")) | .key' | while read key; do
             original_entry=$(git show origin/main:package-lock.json | jq ".packages[\"$key\"]")
             jq --tab --arg key "$key" --argjson entry "$original_entry" '.packages[$key] = $entry' package-lock.json > tmp.$$.json && mv tmp.$$.json package-lock.json
           done
 
           # Commit the change back to the PR branch
           # Amend the Release Please commit to include our fixes
           # This keeps the PR clean with a single commit
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
           git add packages/project/package.json package-lock.json
           git commit --amend --no-edit
           git push --force-with-lease
@@ -116,4 +119,4 @@ jobs:
         working-directory: packages/cli
         run: |
           echo "🚀 Publishing @ui5/cli"
-          npm publish --access public --tag next
+          npm publish --access public --tag next