Previously, ActionView was forced to load by the agent before ActiveSupport
loaded its code, causing any application-defined initializers related
to ActionView to be ignored.
Subscribing after ActiveSupport loads ActionView resolves the problem.

The central argument around loading the agent before other
initializers is to allow initializers to reference the add_method_tracer
API. Including the modules before other initializers are run
allows this to happen.

If the second initializer doesn't specify when it should be run, it
will run immediately after our first initializer. By specifying after:
:load_config_initializers, the agent will not execute init_plugin until
after initializers defined in config/initializers are run. This stops
the agent from forcing ActiveRecord to load before customer-defined
initializers.

The previous instructions were not compatible with Zsh.
These instructions work with Zsh and bash.

Starting the agent after :load_config_initializers prevents the dynamic
initializer for roadie-rails from running, making the gem moot. The customer
who used the bugfix also had an error pop up with one of their
initializers. Though this change solves the problem with configs getting
applied, it may interact unpredictably with existing initializers.
We won't turn on this behavior by default until a major version release.

…-agent-initialization