Stop setting original image annotation on auto-upgrade apps (#1774)

[g-linville]

for #1774

There was an issue related to this original image annotation and nested auto-upgrade apps that use a pattern. The image pattern (i.e. ghcr.io/g-linville/myimage:v#.#.#) would be displayed instead of the actual running image when the user ran acorn ps. For nested auto-upgrade apps, unlike other nested apps, the status.AppImage.Name field is set to the actual, proper image name, so we can just utilize that and not set the original image annotation on them at all, and that fixes the problem.

Checklist

• The title of this PR would make a good line in Acorn's Release Note's Changelog
• The title of this PR ends with a link to the main issue being address in parentheses, like: This is a title (#1216). Here's an example
• All relevant issues are referenced in the PR description. NOTE: don't use GitHub keywords that auto-close issues
• Commits follow contributing guidance
• Automated tests added to cover the changes. If tests couldn't be added, an explanation is provided in the Verification and Testing section
• Changes to user-facing functionality, API, CLI, and upgrade impacts are clearly called out in PR description
• PR has at least two approvals before merging (or a reasonable exception, like it's just a docs change)