v0.8.0 - Add disabling SSL checks, modified query result transformation, support new ruby versions

Thanks for your feedback, which finally lead to this new release!

• new features
  • the configuration wizard now supports accessing grafana, also with unsigned and invalid SSL certificates (#48)
    • the configuration wizard now checks, if your grafana is using a valid SSL certificate:
      • If this is not the case (e.g. it is self-signed), it provides you the possibility to configure your self-signed certificate file.
      • If this is also not working for your installation (e.g. the certificate is expired), it also allows disabling any SSL check. Anyway, you should NOT use the disabling over unsecure channels, as e.g. the internet.
  • By having the new options for configuring SSL through the wizard in the configuration file, the --ssl-cert command line option has now been removed (which was anyway not reasonable, as the reporter supports multiple grafana deployments within the same report, but those grafana deployments can for sure have different certificates...).
  • the default behavior of calling the query value transformations in the order: format, replace_values, filter_columns, transpose can now be changed, by specifying the order in after_fetch (which is being called directly after the query results have been received from the database; default: filter_columns) and after_calculate (which is being called after value calculations as e.g. select_value have been applied; default: format,replace_values). To get the previous behavior, you might set the configuration as after_fetch="",after_calculate="format,replace_values,filter_columns,transpose".
  • a new transformation transpose! (with an exclamation mark!) has been introduced in addition to the existing transpose. The new transformation will always enforce to transpose a query, independent of the additional configuration transpose=true, which is required for the old transpose transformation. I am not so happy with this change, but at least it ensures backward compatibility...
• improvements
  • windows executables are now built with standard AppVeyor ruby versions (currently ruby 3.2.4), to reduce potential security issues with old versions
  • issues, which might happen because of impossible value translations of replace_values (e.g. applying float formatting on a string value) now won't destroy your reports anymore, but will keep the database result instead in the report. From now on, you only receive a warning on the console log.
• bugfixes
  • fixed several bugs, which occured because of supporting newer ruby versions

Enjoy!