[superseded] badge for freebsd,openbsd now reflect latest commit to devel, not latest PR; add badge for new Packages CI

[timotheecour]

• updated badge for freebsd/openbsd:
  builds.sr.ht quickly reacted to my feature request of making their badges meaningful (see https://todo.sr.ht/~sircmpwn/builds.sr.ht/276) so they now reflect latest commit to devel, not latest PR build which is rather meaningless
• added badge for new package CI
• see https://github.com/timotheecour/Nim/blob/pr_fix_badge_builds_sr_ht_openbsd_freebsd/readme.md

[Clyybber]

Whats the purpose of these badges actually?
IMO they only serve to detract potential Nim users because of unrelated CI failures.

[timotheecour]

For new visitors, it actually shows a project is maintained and tested rigorously, on many platforms.
For contributors, it surfaces errors so they get fixed fast. "out of sight, out of mind"

unrelated CI failures

actually badges help distinguishing "unrelated CI failures" in your PR vs "caused by your PR", because they tell show you the state as of last commit.

[Clyybber]

We have decided to only leave the Azure CI badge there, so I'm closing this.

[timotheecour]

@Clyybber What's the rationale for removing them (or please link to discussion where this was discussed), and can we have those badges in some other markdown file in nim repo if not on the top-level readme; they are useful.

Azure badges only reflect part of what's under CI; since we're testing other pipelines, these should be shown too, it's just good testing hygiene / standard practice.

[Clyybber]

The rationale was that they look ugly, clutter the readme and don't provide anything to people checking out the readme. (And they detract potential users when they are red)
Also neither rust or go have them in their readme either (I guess for the same reasons)