feat(react-server): client error boundary for server error

[hi-ogawa]

• (client) error boundary
  • csr
  • two pass ssr
    • Cannot do two-pass SSR? (Even if render two-pass, CSR cannot hydrate it anyway?)
      Does next.js give up SSR and CSR only on 2nd pass?
    • actually giving up SSR is not a big deal in terms of SEO as long it puts <meta>?
  • ssr full csr fallback
    • assets?
    • csr createRoot + render?
  • reset
    • probably need better client-side router + transition integration first?
• http status code
• handle not found via error boundary
• default root error boundary
• convention
• cleanup error log
• test
  • 404, 500
  • browser error
  • reset
• self-reference workaround until Vite 5.2
• move off refactoring to a separate PR
  • refactor(react-server): simplify self-reference workaround #213
• custom server error payload by extending ReactServerErrorContext
  • test

future

• error reset
• redirection as error
• why extra <div> needed for error boundary?