CI broken on Zephyr v4.2 branch

[wearyzen]

Describe the bug

CI failed on #100299 a PR to backport changes to v4.2 branch.
Another PR with same failure : #100407

Regression

• This is a regression.

Steps to reproduce

Open a backport PR on v4.2 branch and ci will fail with below error:
https://github.com/zephyrproject-rtos/zephyr/actions/runs/19966094668/job/57258781296?pr=100299

Relevant log output

Run junitparser merge artifacts/*/*/twister.xml junit.xml
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.12.12/x64/bin/junitparser", line 7, in <module>
    sys.exit(main())
             ^^^^^^
  File "/opt/hostedtoolcache/Python/3.12.12/x64/lib/python3.12/site-packages/junitparser/cli.py", line 91, in main
    return merge(paths, args.output, args.suite_name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/hostedtoolcache/Python/3.12.12/x64/lib/python3.12/site-packages/junitparser/cli.py", line 13, in merge
    result += JUnitXml.fromfile(path)
              ^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/hostedtoolcache/Python/3.12.12/x64/lib/python3.12/site-packages/junitparser/junitparser.py", line 783, in fromfile
    tree = etree.parse(file)  # nosec
           ^^^^^^^^^^^^^^^^^
  File "src/lxml/etree.pyx", line 3711, in lxml.etree.parse
  File "src/lxml/parser.pxi", line 2019, in lxml.etree._parseDocument
  File "src/lxml/parser.pxi", line 2045, in lxml.etree._parseDocumentFromURL
  File "src/lxml/parser.pxi", line 1946, in lxml.etree._parseDocFromFile
  File "src/lxml/parser.pxi", line 1222, in lxml.etree._BaseParser._parseDocFromFile
  File "src/lxml/parser.pxi", line 642, in lxml.etree._ParserContext._handleParseResultDoc
  File "src/lxml/parser.pxi", line 760, in lxml.etree._handleParseResult
  File "src/lxml/parser.pxi", line 682, in lxml.etree._raiseParseError
OSError: Error reading file 'artifacts/*/*/twister.xml': failed to load "artifacts/*/*/twister.xml": No such file or directory
Error: Process completed with exit code 1.

Impact

Annoyance – Minor irritation; no significant impact on usability or functionality.

Environment

No response

Additional Context

No response