test(e2e): ensure proper cleanup of build after execution

[chenjiahan]

Summary

Ensure proper resource cleanup after the E2E build process.

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[netlify]

✅ Deploy Preview for rsbuild ready!

Name	Link
🔨 Latest commit	cdc4ba8
🔍 Latest deploy log	https://app.netlify.com/projects/rsbuild/deploys/68539b030df69f00072a8346
😎 Deploy Preview	https://deploy-preview-5441--rsbuild.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 85 (🔴 down 2 from production) Accessibility: 97 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 60 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull Request Overview

This PR ensures that the build’s internal resources are cleaned up by capturing and invoking the close callback returned from rsbuild.build().

• Store the build-close function (result.close) in closeBuild
• Invoke closeBuild before shutting down the preview server and restoring console proxy
• Update the cleanup logic in the returned close handler

Comments suppressed due to low confidence (2)

e2e/scripts/shared.ts:283

• [nitpick] Add a brief comment explaining what closeBuild represents and when it might be undefined to aid future maintainers.

  let closeBuild: () => Promise<void> | undefined;

e2e/scripts/shared.ts:331

• Consider adding an E2E or unit test that verifies closeBuild is actually invoked and that build-related resources are released correctly.

      await closeBuild?.();