Use backlogger to provide the backlog status

[kalikiana]

We can benefit from shared upstream code used by multiple projects and simplify this project to the configuration of queries and metadata. The most visible impact is that changing queries becomes trivial.

This will also enable use of new features such as influxdb output and computation of metrics once they're implemented.

See: https://progress.opensuse.org/issues/121582

[kalikiana]

Note: This is not required by poo#113797 but I prepared the queries.yaml on the side since I wanted to check if the code was still re-usable. Currently the queries won't issue reminders since they don't have update_on or due_date in them.

[kalikiana]

Note: This is not required by poo#113797 but I prepared the queries.yaml on the side since I wanted to check if the code was still re-usable. Currently the queries won't issue reminders since they don't have update_on or due_date in them.

In the context of poo#121582 this is becoming even more useful in tandem with openSUSE/backlogger#15 which allows feeding the same queries into Grafana.

[okurz]

Sorry, I don't quite understand the impact of the change.
The commit message could have a bit more details, e.g. what issue is fixed, why this needs to change, to which versions of which product it applies, link to a bug or a fate entry, the choices you made, etc. Also see https://commit.style/ or http://chris.beams.io/posts/git-commit/ as a helpful guide how to write good commit messages.