fix: enforce working-directory for act_runner host mode compatibility

CRITICAL FIX: Resolve act_runner host mode working directory issue

Problem:
- act_runner host mode does not persist working directory between steps
- Each 'cd repo' command was being lost due to isolated step execution
- npm install was still running in hostexecutor directory instead of repo

Solution:
- Add 'working-directory: repo' to every step after clone
- Enforce working directory at step level instead of inside run commands
- This bypasses act_runner host mode quirks completely

Changes:
- Update all 7 workflows to use working-directory: repo
- Remove 'cd repo' from run commands (redundant with working-directory)
- Keep git clone step outside working-directory (needs to run in default dir)
- Add verification steps to confirm correct working directory

Workflows updated:
- ci.yml, audit.yml, fix.yml, test.yml, security-scanning.yml
- cli-level1-tests.yml, ci-cd.yml

This should finally resolve the ENOENT: no such file or directory
errors for package.json by ensuring all npm commands execute in the
correct repository directory.

.gitea/workflows/test.yml

@@ -15,8 +15,8 @@ jobs:
           git clone https://gitea.bubuit.net/oib/aitbc.git repo
 
       - name: Verify repository context
+        working-directory: repo
         run: |
-          cd repo
           echo "Current working directory:"
           pwd
           echo "Files in directory:"
@@ -25,13 +25,12 @@ jobs:
           ls -la package.json || echo "package.json not found"
 
       - name: Install dependencies
-        run: |
-          cd repo
-          npm install --legacy-peer-deps
+        working-directory: repo
+        run: npm install --legacy-peer-deps
 
       - name: Test runner
+        working-directory: repo
         run: |
-          cd repo
           echo "Runner OK"
           hostname
           whoami