[CI] optimize JUnit report generation for backend tests (#28584)

.github/actions/test-driver/action.yml

@@ -23,8 +23,10 @@ runs:
       shell: bash
     - name: Publish Test Report (JUnit)
       uses: dorny/test-reporter@v1
-      if: always()
+      if: failure()
       with:
         path: 'target/junit/**/*_test.xml'
         name: JUnit Test Report ${{ inputs.junit-name }}
         reporter: java-junit
+        list-suites: failed
+        list-tests: failed

.github/workflows/backend.yml

@@ -139,11 +139,13 @@ jobs:
 
     - name: Publish Test Report (JUnit)
       uses: dorny/test-reporter@v1
-      if: always()
+      if: failure()
       with:
         path: 'target/junit/**/*_test.xml'
         name: JUnit Test Report be-tests-java-11-ee-pre-check
         reporter: java-junit
+        list-suites: failed
+        list-tests: failed
 
   be-tests:
     needs: files-changed
@@ -174,11 +176,13 @@ jobs:
 
     - name: Publish Test Report (JUnit)
       uses: dorny/test-reporter@v1
-      if: always()
+      if: failure()
       with:
         path: 'target/junit/**/*_test.xml'
         name: JUnit Test Report be-tests-java-${{ matrix.java-version }}-${{ matrix.edition }}
         reporter: java-junit
+        list-suites: failed
+        list-tests: failed
 
   be-tests-stub:
     needs: files-changed