Fix junit report generation

[fjglira]

Fix the junit report generation for every test run for our e2e test execution

What type of PR is this?

• Enhancement / New Feature
• Bug Fix
• Refactor
• Optimization
• Test
• Documentation Update

What this PR does / why we need it:

We are having issues generating the Junit report for test executions. This PR aims to fix these issues to ensure the report is generated whatever the test execution pass or fails

Which issue(s) this PR fixes:

Fixes #1217

Related Issue/PR #

Additional information:

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.61%. Comparing base (5fe7836) to head (de98cfd).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1218      +/-   ##
==========================================
+ Coverage   77.50%   77.61%   +0.10%     
==========================================
  Files          44       44              
  Lines        2823     2823              
==========================================
+ Hits         2188     2191       +3     
+ Misses        527      525       -2     
+ Partials      108      107       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[istio-testing]

In response to a cherrypick label: new pull request created: #1219

[istio-testing]

In response to a cherrypick label: #1218 failed to apply on top of branch "release-1.25":

Applying: Fix junit report generation
Using index info to reconstruct a base tree...
M	tests/e2e/common-operator-integ-suite.sh
Falling back to patching base and 3-way merge...
Auto-merging tests/e2e/common-operator-integ-suite.sh
CONFLICT (content): Merge conflict in tests/e2e/common-operator-integ-suite.sh
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Fix junit report generation

[istio-testing]

In response to a cherrypick label: new issue created for failed cherrypick: #1220

[istio-testing]

In response to a cherrypick label: new pull request could not be created: failed to create pull request against istio-ecosystem/sail-operator#release-1.26 from head istio-testing:cherry-pick-1218-to-release-1.26: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for istio-testing:cherry-pick-1218-to-release-1.26."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

[istio-testing]

In response to a cherrypick label: new pull request created: #1221

[istio-testing]

In response to a cherrypick label: new pull request could not be created: failed to create pull request against istio-ecosystem/sail-operator#release-1.26 from head istio-testing:cherry-pick-1218-to-release-1.26: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for istio-testing:cherry-pick-1218-to-release-1.26."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

[istio-testing]

In response to a cherrypick label: new pull request could not be created: failed to create pull request against istio-ecosystem/sail-operator#release-1.27 from head istio-testing:cherry-pick-1218-to-release-1.27: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for istio-testing:cherry-pick-1218-to-release-1.27."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

[istio-testing]

In response to a cherrypick label: new pull request could not be created: failed to create pull request against istio-ecosystem/sail-operator#release-1.27 from head istio-testing:cherry-pick-1218-to-release-1.27: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for istio-testing:cherry-pick-1218-to-release-1.27."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}