refactor(general): add running allure report flow after forge ci job …

…part 3 (#1023)

* add running allure report flow after forge ci job

* add temp trigger for this branch

* try 1

* try 2

* try 3

* try 4

* add running after ci finishes

* try using forge run instead of ci run

* try using forge run instead of ci run for all possible in allure flow

* add forge setup step

* try 1

* try 2

* try 3

* try 4

* add forge install

* cleanup

* remove running allure after ci until allure flow changes are in main

* remove local running option

* remove unused vars

* add running test reporting after ci job

* add running test reporting after ci job

* remove allow-privileged flags from disabled tests

* cleanup

.github/workflows/ci.yml

@@ -18,6 +18,7 @@ jobs:
     with:
       forge_version: 0.2.1
 
-  allure:
+  test_reporting:
+    if: always()
     needs: ci
     uses: input-output-hk/catalyst-voices/.github/workflows/generate-allure-report.yml@main

.github/workflows/generate-allure-report.yml

@@ -45,7 +45,6 @@ jobs:
         continue-on-error: true
         with:
           path: ./catalyst-gateway/tests/schemathesis_tests+test-fuzzer-api
-          target_args: --allow-privileged
 
       - name: Get flutter unit test report
         uses: input-output-hk/catalyst-forge/actions/run@master
@@ -60,7 +59,6 @@ jobs:
         continue-on-error: true
         with:
           path: ./catalyst-gateway/tests/api_tests+test
-          target_args: --allow-privileged
 
       - name: Collect and upload test reports
         uses: actions/upload-artifact@v4