Heptapod CI Docker: tagging stable testing images

We've always been tagging the produced image as testing (for registry.h.n anyway), but it turns out to be confusing when building for both heptapod and heptapod-stable in short succession. This can happen when there are upstream security updates for both branches (in particular meaning that both branches are released and alive, which didn't happen much in the past).