[browser-esbuild] live-reload=false workflow is less convenient now

### Command

serve

### Description

I often work with `live-reload` disabled. This is helpful when working on CSS changes, I can try things in browser and then make multiple edits in files before manually reloading.
It's also faster when working on a laptop.

Before esbuild:
1. Make changes.
2. Refresh page.
3. Page reloads after new changes have been compiled.

With esbuild:
1. Changes.
2. Refresh.
3. Page reloads immediately before changes have been compiled. Now I need to monitor terminal and reload the page after successful compilation.

### Describe the solution you'd like

I was okay with the old behaviour where server wouldn't respond before successful compilation.

A less desired alternative would be to log Vite messages in browser's console, so that I can tell when compilation has finished there.

### Describe alternatives you've considered

_No response_

Inizia con il workflow del comando `serve` con `live-reload=false` e traccia il comportamento delle richieste del browser mentre esbuild compila le modifiche. Riproduci la sequenza di aggiornamento, quindi verifica che un aggiornamento attenda il completamento con successo della compilazione oppure che il completamento della compilazione venga mostrato nella console del browser.

Scritto dal modello di indicizzazione a partire dal testo della issue.