Standardize in the backend health check for the Zabbix datasource

[andresmgot]

I noticed that the health check for the Zabbix datasource is failing for the Advisor but in the data source configuration page, it does work. This is because the Advisor is running the backend version of the health check, while the Config editor uses the frontend one.

Since the backend health check is something that can be used for external tooling, it makes sense to use that one by default. For doing so, it will be needed to remove the method testDatasource from the frontend and extend the DatasourceWithBackend class that @grafana/runtime exposes or manually implement it as the library does.

[apoeCivir]

Hi believe that what you mean is what I have encountered when trying to monitor the zabbix datasource with zabbix itself.
In the frontend everything looks good (grafana 12.2, zabbix 7.2.5 and zabbix plugin 6.0.2)

But when calling the datasource health API it returns:

curl -X GET -k -u admin:<admin-password> https://localhost:3000/api/datasources/uid/bf0wuhjjprsw0a/health {"message":"Invalid request. Invalid parameter \"/params\": an array or object is expected.","status":"ERROR"}
Same happens if I use deprecated call with id, instead of uid.