Use Visualizations to render API.processedReport to add display properties / report settings

[tsteur]

We will need this for API.getProcessedReport when making more use of AngularJS to render all the reports client side. The Visualization would add several ViewDataTable/Config and ViewDataTable/RequestConfig properties to the report metadata. We will need this in Piwik itself eg to decide whether we have to show footer icons, whether to show a search box, whether to show a filter_limit selector, the default number of rows per datatable, etc. The same is needed for Piwik Mobile see eg matomo-org/matomo-mobile-2#3241 and #3780 to display the reports the same way across apps.

[tsteur]

This will be needed for #7131 and #4734 . This will allow us to no longer need the $report instance to render a report. Instead we will render based on the API output (in the browser possibly but not necessarily).

Possible problems
We currently define for example filters for API output in configureVieweg https://github.com/piwik/piwik/blob/2.13.0-rc3/plugins/Actions/Reports/Base.php#L47 . This is no good. This should be actually handled in the visualization itself and/or API.getProcessedReport see #7072