Fix template usage

[Owen Arnold]

Entire Presenters in VatesAPI are templated with the ViewType because cannot force Paraview Filters to multi-inherit. This is due to code magic on the Paraview side which is doing source-code editing under the hood.

The problem is that these header files are getting big now and am concerned about template bloat owing to the member templates.

Don't actually need to template the entire presenter. can template concrete separate ViewAdaptee types for MDLoadingView and MDRebinningView. That way all templated code can be taken out of the presenters. See attached UML 2 diagram.

These types will no longer need to be templated:

• EventLoadingPresenter
• MDEWLoadingPresenter
• MDLoadingPresenter
• MDEWEventNexusLoadingPresenter
• MDEWRebinningPresenter
• MDHistogramRebinningPresenter

These small templated types will be created:

• MDLoadingViewAdapter
• MDRebinningViewAdapter

These abstract types will not change at all:

• MDLoadingView
• MDRebinningView

[Owen Arnold]

Show also unit test adaptee wiring-ups. Ensure that the adpaters are using the adaptees properly!

[Owen Arnold]

In [14463]:

refs #3677 #3662. 3677 will probably involve adapting/extending the MVP presenters to handle loading from the ADS rather than files. Needed to fix template usage anyway.

[Owen Arnold]

In [14464]:

refs #3677 #3662. Strip includes out of header files now that not templated.

[Owen Arnold]

In [14465]:

refs #3677 #3662. Fix warning.

[Michael Reuter]

I believe this is working just fine as I have been leaning on the plugins quite hard during the Vates simple interface plugin project and nothing out of the ordinary happened.

[Stuart Campbell]

This ticket has been transferred to github issue ​4509