Package Scenery into analyzer for analysis and report generation

Causality-wise it would make more sense to pass the scenery as an argument to the analyzer and store it in the analyzer variant and then call the functions "analyze" or "report".

Then, the report depends on the analyzertype (which it already does) and also it is the analyzer which analyzes the scenery and not the scenery itself.

This may come in more useful for analyzertype-specific pdf reports (for example a scenery ray-trace plot).

Probably, this only needs some wrapping of functions. But then, one can use the analyzer, as well as the scenery informaion during the report, which is currently not given in the pdfreportable trait