test: fix typos in image discovery fixtures and test text

[luojiyin1987]

Description

Fix several typo-only changes under src/:

• test case text in src/internal/api/v1alpha1/validate_test.go
• comment text in src/pkg/packager/publish_test.go
• scratch fixture names in find-images testdata
• a container name typo in valid-image-uri testdata

The fixture renames were checked to ensure they do not change image discovery behavior.

Tests run:

• go test ./src/internal/api/v1alpha1 -run TestValidateChart
• go test ./src/pkg/packager -run 'TestFindImages/(valid-image-uri)$|TestFindImages/(images found in archives)$|TestFindImages/(images found in different archives)$'\n\n## Related Issue\nRelates to Fix typos in tests and image discovery fixtures #4944\n\n## Checklist before merging\n- [x] Test, docs, adr added or updated as needed\n- [ ] Contributor Guide Steps followed\n\nCommits are GPG-signed. This PR is opened as draft because the branch still needs commit sign-off (Signed-off-by) to satisfy the contributor guide before merge.

[netlify]

✅ Deploy Preview for zarf-docs canceled.

Name	Link
🔨 Latest commit	e00f8ea
🔍 Latest deploy log	https://app.netlify.com/projects/zarf-docs/deploys/6a18519b8d726a0008644ce5

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[brandtkeller]

Appreciate the PR - minor feedback otherwise straight forward. would love to hear more about what noise you are getting from the typos and any tooling recommendations you might have.

[luojiyin1987]

Appreciate the PR - minor feedback otherwise straight forward. would love to hear more about what noise you are getting from the typos and any tooling recommendations you might have.

Thanks. This wasn’t causing much trouble in practice. I was already reading through the code and ran typos during that pass, and it surfaced a few small wording/spelling inconsistencies like this one.

No strong recommendation from me beyond using typos as a lightweight optional check locally or in CI.