v1.63.1

Three fixes, all of them found by questions in the issue tracker rather than by anything going wrong.

On a mixed-architecture fleet, every host after the first was checked against the wrong platform. The daemon's architecture was cached once per process instead of per host, so an arm64 box sitting next to an x86 one — an ordinary homelab — had its multi-arch images compared against amd64 digests and got the wrong answer every time. Multi-host setups only. @LeeNX asked in #7 how mixed environments would behave, which is how this surfaced, before anyone had actually run one that way.

While fixing it I found the parsing was fragile too: a platform string containing more than one slash fell through to the amd64 default rather than being read. Falling back is right when the daemon says nothing; it's wrong when the daemon answered and we simply failed to parse it.

The Web UI linked to a project's front page where the bot linked to its releases page. The Web UI keeps its own copy of the link priority chain so it doesn't have to inspect every container just to draw the table — and that copy was missing the rewrite. Same container, two different links depending on where you looked. @LeeNX spotted it on Docksentry's own row in #52.

Gitea and Forgejo repo links now point at the release too. They mirror GitHub's layout closely enough that /releases/latest resolves — @LeeNX proved it with the redirect. Covers gitea.com, Codeberg and self-hosted instances. A manual docksentry.link label or /setlink is still never rewritten; that's your choice to make.