Reinitialize controller_class renderer with connection.env

[leastbad]

Type of PR (feature, enhancement, bug fix, etc.)

Bug fix

Description

Assuming people use the render method, this initializes the mock controller renderer instance with the connection.env.

We should update the docs to say that if people use ArbitraryController.render then they should actually use ArbitraryController.renderer.new(connection.env).render instead.

Why should this be added

Should prevent "session bleed".

Testing

# app/helpers/home_helper.rb
module HomeHelper
  def shitblast
    "yummy"
  end
end

<div class="card-body d-flex justify-content-center">
  <div id="test"></div>
  <button class="btn btn-dark" type="button" data-reflex="click->Example#renderer">Test</button>
</div>

<%# app/views/home/_test.html.erb %>
<%= current_user.name %><br>
<%= shitblast %><br>
<%= home_path %><br>
<%= render partial: "home/test2" %>

<%# app/views/home/_test2.html.erb %>
Yowza!
<%= current_user.name %><br>
<%= shitblast %><br>
<%= home_path %><br>

class ExampleReflex < ApplicationReflex
  def renderer
    morph "#test", render(partial: "home/test")
  end
end

Checklist

• My code follows the style guidelines of this project
• Checks (StandardRB & Prettier-Standard) are passing
• This is not a documentation update