Proceed with the official first iteration of the Nvchecker PoC bumpbuddy

As discussed with @gromit, we think this PoC has been running reliably for enough time to stop considering as a PoC and announce the first official iteration of this project. This issue serves as a task listing & tracking for it.

Here are my short-ish term goals toward officially announcing the introduction of this project and spread its usage through our packagers:

• Remove the PoC mention and rename the project to a proper name

  • This includes renaming this repo, directories & files on the dedicated server, code where needed (e.g. systemd units) and so on...
  • For the name, bumpbuddy seemed like a fairly appreciated choice and it goes along with our other bots' naming scheme such as bugbuddy, gluebuddy and killbuddy (dafuk is that? 🤣 TIL I guess 😅).
  • rename https://gitlab.archlinux.org/nvchecker

• Write the Ansible code for the dedicated server (and open the related MR in the infra repo).

• Remove the hardcoded limiter (see https://gitlab.archlinux.org/archlinux/nvchecker-poc/-/merge_requests/3#note_233471) for monitored packages to start monitoring every of them (and check if nothing explode).

• Create initial tag (v1.0.0)

• Write a mail to ADP to introduce bumpbuddy to the world, including current spec, remaining stuff to tackle and future mid / long term goals.

I intend to start working on those tasks sometimes next week 🙂
Feel free to leave a comment or ping me if you wanna share some thoughts, do some pair work or whatever 🤗