Remove dev server restart workaround since flakiness is presumably fixed

Author: eps1lon

test/development/app-hmr/hmr.test.ts

@@ -138,11 +138,6 @@ describe(`app-dir-hmr`, () => {
     })
 
     it('should update server components pages when env files is changed (nodejs)', async () => {
-      // If "should update server components after navigating to a page with a different runtime" failed, the dev server is in a corrupted state.
-      // Restart fixes this.
-      await next.stop()
-      await next.start()
-
       const envContent = await next.readFile(envFile)
       const browser = await next.browser('/env/node')
       expect(await browser.elementByCss('p').text()).toBe('mac')
@@ -191,10 +186,6 @@ describe(`app-dir-hmr`, () => {
     })
 
     it('should update server components pages when env files is changed (edge)', async () => {
-      // Restart to work around a bug highlighted in the flakiness of "should update server components after navigating to a page with a different runtime"
-      await next.stop()
-      await next.start()
-
       const envContent = await next.readFile(envFile)
       const browser = await next.browser('/env/edge')
       expect(await browser.elementByCss('p').text()).toBe('mac')