Generalize special case of loading plugin classes for LeverageStep

There is an odd special case in the pipeline code where the Leverage Step is handled differently because it can pull in additional plugins. The purpose of this patch is to weaken this coupling by extracting a couple of methods into an interface for steps that need to pull in additional classes.

(The ultimate goal of this is to allow me to exclude the leverage step at build and run time.)