jtreg failure handler pages are mislabelling the jcmd/thread/dump_to_file results.

jtreg failure handler pages are labelling jcmd/thread/dump_to_file results with the wrong PID. The right files are actually there if you manually change the link.

e.g.
11904
  common
    jcmd
      thread
        dump_to_file

iteration_0
----------------------------------------
[...] [...\windows-x64-debug.jdk\jdk-22\fastdebug\bin\jcmd.exe, 11904, Thread.dump_to_file, -format=json, JavaThread.dump.11904.0] timeout=20000
----------------------------------------
11904:
Created .....\testoutput\test-support\jtreg_open_test_jdk_jdk_jdi\scratch\4\JavaThread.dump.11904.0
----------------------------------------
[...] exit code: 0 time: 583 ms
----------------------------------------
JavaThread.dump.11888.5


If we expand pid 11904, it says it's creating JavaThread.dump.11904.0 (which it does!), but always links to JavaThread.dump.11888.5

11888 was an earlier Java process which had artifacts gathered.