Move object_with_translations into the plan base class

Objects and objects that have their inputs translated (object and object_with_translations subroutines, respectively) should be fully created in the plan base class instead of during entry processing. 

For the reporter object this means that filters and interpreters are attached during object creation and all inputs (of the reporter itself as well as the attached filters and interpreters) are translated. This is achieved by overwriting object and object_with_translations in the reporter plan child class.
The filters and interpreters are stored as a hash, keyed on their name so when the translated filters and interpreters are added, the untranslated versions are being overwritten. However, I will add a test to ensure that that is the case. Certainly not ideal so if you can think of a way for it to call the base class's object instead of the reporter plan's object subroutine, that would be even better.