test(dev): expect a hot update across a circular import - #10700

Fix dev test ci error found in #10699

The dev-server harness builds whatever `vitejs/vite` `rolldown-canary` rebased onto `main` gives it, so this arrived without any rolldown change: the last green run is 06:12Z and the first red one is 07:39Z, with vitejs/vite#23259 landing at 07:26Z between them. Every `Node Dev Server Test` job has been red since, on every branch and every Node version, including `main`.

### The playground

```
main.js  →  a.js  →  b.js  ⇄  c.js
   ↑                    b and c import each other
   └── only main calls import.meta.hot.accept()
```

### What changed upstream

Editing `c.js` makes the HMR client walk up the importers looking for a module that accepts updates:

```
c.js → imported by b; b does not accept, keep going
b.js → imported by a and by c
         via a: a → main, and main accepts ✓
         via c: that is where the walk started, it loops back
```

It used to drop the whole walk the moment it looped back — including the `main` boundary it had already found — and reload the page:

```
full reload needed: circular import chain between `b.js` and `c.js`
```

vitejs/vite#23259 makes it skip the path it already walked and keep the boundary it found, so the edit is applied through `main` and the page stays. Vite's unbundled dev has behaved this way since vitejs/vite#14867; bundled dev was the outlier.

### Why the test broke

`hmr-accept-outside-circular` pinned the old behavior: wait for that log line, then assert the page reloaded (a marker planted on `window` is gone). Neither holds now — the log is deleted, so the wait times out with `Timeout waiting for browser logs`, and the marker survives.

The spec now asserts the hot update: the edit renders and the marker survives. The marker also carries the original guarantee, which the log used to carry — if the walk missed `main`'s boundary entirely, the page would reload and wipe it, so a "content is fresh" assertion alone cannot pass by accident.

Validation: the full browser suite passes locally against Vite `main` at c0f2fc607, which contains the change — 104 passed / 12 skipped, exactly CI's counts with the one failure flipped. Not verified: the new assertion has not been run against a pre-#23259 Vite.