fix: resolved offerings: calculate if a container is missing

[g-linville]

We saw cases (involving nested acorns) where resolved offerings would have containers missing from the list entirely. I think this was due to weird behavior where the .Status.AppStatus.Containers would not be populated on a nested acorn the first time it ran through the resolved offerings handler. To make sure that everything ultimately gets resolved, I added this new needsCalculation function that checks to make sure that every container defined in the app is also present in the resolved offerings.

Checklist

• [x] 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
• [x] All relevant issues are referenced in the PR description. NOTE: don't use GitHub keywords that auto-close issues
• [x] 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
• [x] 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)

[g-linville]

Sorry @thedadams and @StrongMonkey. I just requested your re-review. While working on other stuff, I figured out the real problem with container.Name. Sometimes it just wasn't set at all for whatever reason. So I changed up the function that creates the resolved offerings annotation to just take the name of the container as a string, and I pass it all the way down to there.