Add back support for SSR error boundaries

[chrisetheridge]

Is your feature request related to a problem? Please describe.
Currently you cannot properly implement SSR error boundaries, because the results of the error boundary render function are not processed by the SSR HTML renderer.

Describe the solution you'd like
I would like to be able to write an error boundary that can be used in both the JVM and JS. I can just do plain old try + catch, but that means we can't easily share component logic between platforms.

Describe alternatives you've considered
I've tried using try + catch on the JVM and that works. But this means you need 2 different component implementations when you want to use error boundaries, or at least 2 different component wrapper implementations.

I've also tried using error boundaries as they are now, but the returned UIx element is not compiled by the HTML renderer.

(defn create-error-boundary [{:keys [render-fn derive-error-state did-catch
                                     display-name]}]
  (fn [& args]
    (try
      (render-fn (atom nil) args)
      (catch Exception e
        (did-catch e display-name)
        (render-fn (atom (derive-error-state e)) args)))))

(def error-boundary
  (create-error-boundary
   {:derive-error-state (fn [error]
                          {:error error})
    :did-catch          (fn [error info]
                          (logging/error "Component did catch" error)
                          info)}
   (fn [state children]
     (logging/info "Render" @state children)
     (if (:error @state)
       (:error @state)
       children))))

Additional context
I think we can just use the UIx V1 error boundary approach as is, it works pretty well!

[chrisetheridge]

https://github.com/pitch-io/uix/compare/master...chrisetheridge:uix:error-boundary?expand=1

[roman01la]

resolved in #98