Add support for Turbo-streaming ViewComponents.

[joelhawksley]

Closes #1106.

[gap777]

This is surprising. I thought serializable was producing an artifact for passing into ActiveJob, but that renderable was describing something that could render HTML for the front end. Isn't this mixing unrelated things?

[bensheldon]

Conceptually, it's that we're making a renderable that can pass through the Active Job boundary by being serializable.

[bensheldon]

This definitely does what it says it does, and is very simple by simply intercepting new to assign a property. So I'm 👍🏻 on this without any project-lifecycle context.

Specifically as to project lifecycle, I think this API is fairly limiting and I wonder if it becomes difficult to extend. e.g. do the limitations become inherent to this implementation.

I'd offer that one alternative would be to create a Proxy object that looked something like this:

class ViewProxy
  def initialize(target, **kwargs)
    @target = target
    @initialize_kwargs = kwargs
    @with_component_kwargs ||= []
  end
  
  def with_component(**kwargs)
    @with_component_kwargs << kwargs
  end
  # etc. whatever
  
  def render
    @target.new(@initialize_kwargs).then do |instance|
      @with_component_kwargs.each { |k| instance.with_component(**kwargs) }
      # etc.
    end.render
  end
end

module Serializable
  def serializable(**kwargs)
    ViewProxy.new(self.class, **kwargs)
  end
end

MyComponent.serializable(foo: "bar").with_component(foo: "bar")