use vi.stubGlobal to handle change to dom-environment-global-assignme…

[OyvindLGjesdal]

…nts-now-update-the-underlying-window

GitHub issue resolved #

Pull request Description:

Fixes failing build when trying to upgrade to vitest 5.x in dependabots #4229

AI assisted, using the migration docs:

Vitest 5 forwards ordinary global assignments to jsdom’s window, so global.document = … hits its getter-only property.
vi.stubGlobal defines a temporary property and vi.unstubAllGlobals() restores the original descriptor. Migration guide
(https://vitest.dev/guide/migration/#dom-environment-global-assignments-now-update-the-underlying-window) · Vitest API (https://vitest.dev/api/vi)

The PR passes with the changes locally, but the migration guide changes some defaults, as well as other breaking changes. I haven't gotten through the full migration guide yet, but can do a read-through to see if anything else looks relevant, as well.

---

• Tests are included.
• Documentation change and updates are provided for the Apache Jena website
• Commits have been squashed to remove intermediate development commit messages.
• Key commit messages start with the issue number (GH-xxxx)

By submitting this pull request, I acknowledge that I am making a contribution to the Apache Software Foundation under the terms and conditions of the Contributor's Agreement.

---

See the Apache Jena "Contributing" guide.

[OyvindLGjesdal]

Does any other breaking changes or defaults look relevant for the jena codebase in jena-fuseki-ui?

• I found no other Vitest 5 change that currently requires a code fix in jena-fuseki-ui. The full unit suite and coverage run both passed locally: 8 files, 46 tests.

The migration items most relevant to this project are:

• Requirements and defaults are covered. The UI declares Vite directly, Maven installs Node 24.16.0, and clearMocks: true is already explicit. Vitest migration guide (https://vitest.dev/guide/migration/) ·
  jena-fuseki2/jena-fuseki-ui/package.json:77 · jena-fuseki2/jena-fuseki-ui/vite.config.js:78

• Coverage matching changed. The UI has custom coverage.exclude patterns, so coverage is worth comparing with an earlier report if exact file coverage matters. Vitest 5 produced a report successfully; I did
  not compare its file set against Vitest 4. Migration guide (https://vitest.dev/guide/migration/#coverage-include-and-exclude-match-more-precisely) · jena-fuseki2/jena-fuseki-ui/vite.config.js:92

• Report artifact paths changed. The UI’s jena-fuseki2/jena-fuseki-ui/.gitignore:1 does not include .vitest/. That only needs attention if the project uses Vitest’s HTML, JSON, JUnit, or blob report output.
  Migration guide (https://vitest.dev/guide/migration/#generated-reports-and-artifacts-use-the-vitest-directory)

I found no uses of the removed sequencing APIs, hoisted mocks inside callbacks, unawaited async assertions, or browser mode features described in the guide.