Error messages should say which pin they are about

[antifuchs]

So far it's happened to me a few times that npins, when operating on all pins, has had an issue with a single repository and wrote an error like:

[sonarr-plex-cleaner] No Changes
[speedtest_exporter] No Changes
[tailscale/tailscale] No Changes
[tailscalesd] No Changes
Error: Failed to ensure version monotonicity, latest found version is 0.8.3 but current is 0.9.0-rc1

...which doesn't tell me which pin it is upset about (when looking for the version number, I find that the repo is tc_exporter, a name that isn't logged before)

There were a few other instances where I got messages of similar shape, so I think it would be really neat if all of those per-pin messages could say which pin they are concerning.

[Coca162]

This also comes hand in hand in reworking the way we do error handling in general to be less reliant on just anyhow; adding our own error types that can hold the pin the error is on would be very useful.

[antifuchs]

Oh, if this is using anyhow, then it sounds like a few .context calls in a few strategic places might be all that's necessary for really useful debug info! I'll take a quick look.

[antifuchs]

Believe #208 should address all the times that I saw a hard-to-debug error like this.