Migrate "Transformation analyzer" module to V4 report

[ChristopherJennings]

Overview

We should migrate the Transformation analyzer module to the new V4 report format.

Definition of done

• Code and Scripts are ported to KenticoInspector.Reports project in a dedicated folder for the report.
• Scripts are referenced via constants in a static class.
• Scripts are refactored to return simple results that are mappable to simple classes.
• Report logic is covered by unit test for a clean result
• Report logic is covered by unit tests for all known dirty results
• Useful, non-specific logic is abstracted to services or helpers.

Note: The Class/Table Validation report (and it's tests) is a good, simple example of the main concepts.

Additional Details

• New name: Transformation Security Analysis
• Tags: Portal Engine, Security, Transformations

[yuriys-kentico]

I claim ownership!

[yuriys-kentico]

I am unsure how to format the results. I have three ideas:

List of tables by issue type
Each issue will have a separate table, and each row will be the snippet, reason, property details, web part, and template.

Drawback: Repetition of web part and template details.

One table by transformation
Each transformation is a row with the snippets, reason and template usage.

Drawback: Repetition of web part and template details.

One table by template
Each template is a "row" with a nested structure for web parts, their properties, and issues under each transformation. It would look like this:

Drawback: Not sure how to display that in a plain table. Each cell has text wrapping, so it is impossible to maintain cell divisions. Issue reasons could be duplicated in the last column.

I like the last one because it allows a user to see where in a site an issue appears. This context could help locate the transformation on the page and also affect its severity.