CI: Fix find command logic for shell script executable permission check

- Corrected the find command grouping in the permissions workflow to avoid false positives.
- Now, only .sh files (including run.sh) missing user-execute permission are reported.
- Prevents unnecessary errors when all scripts are already executable.

Signed-off-by: Srikanth Muppandam <[email protected]>

Author: smuppand

.github/workflows/check-executable-permissions.yml

@@ -16,7 +16,7 @@ jobs:
       - name: Detect missing executable permissions on shell scripts
         run: |
           # Find all .sh and run.sh scripts without +x
-          BAD=$(find . -type f -name 'run.sh' -o -name '*.sh' ! -perm -u=x)
+          BAD=$(find . -type f \( -name "*.sh" -o -name "run.sh" \) ! -perm -u=x)
           if [ -n "$BAD" ]; then
             echo "::error file=run.sh,line=1::❌ Some shell scripts are missing executable permissions. This can break CI and LAVA. Please fix before merging."
             echo "::error file=run.sh,line=2::To fix, run: find . -name '*.sh' -o -name 'run.sh' | xargs chmod +x && git add . && git commit -m 'Fix: restore executable bits on scripts' && git push"