Stop synthetic test-report check from failing unrelated workflow runs

[Copilot]

mikepenz/action-junit-report publishes a separate check run named test-report. GitHub was surfacing that check as if it were an additional job on the same commit, which made the Pages deployment run appear to fail for a job not defined in pages.yml.

• Workflow behavior

  • Set the JUnit report step in .github/workflows/test.yml to fail_on_failure: 'false'
  • Preserve report publication while avoiding a failing synthetic check that can be misattributed to other workflows on the same SHA

• Documentation

  • Added an inline note explaining that test-report is a generated check run, not a declared workflow job, and why it should not fail the main run

• Relevant change

  - name: Publish surefire test report
    if: always()
    uses: mikepenz/action-junit-report@v6.5.0
    with:
      # This action creates a separate "test-report" check run that GitHub
      # may display as if it were an extra job in other workflows for the same commit.
      check_name: test-report
      report_paths: 'target/*-reports/TEST-*.xml'
      fail_on_failure: 'false'