Handling broken reporting database

reporting.get_data and reporting.get_all will now raise an error 206 if reporting database is broken:

{
"msg": "result",
"id": "45de8359-48a3-1d17-581b-233bb08f50b3",
"error": {
"error": 206,
"type": null,
"reason": "[EINVALIDRRDTIMESTAMP] RRD file aggregation-cpu-sum/cpu-idle.rrd has update time in the future. Data collection will be paused for 16 weeks, 3 days and 17 hours.",
...

Error text should be displayed to the user, explaining why reporting data is unavailable.

Additionally, something like

You can clear reporting database and start data collection immediately by clicking HERE.

should be appended to the message. When clicking, user should confirm destructive action and if they confirm, reporting.clear method should be called.