Fix CONTAINER1015 not showing registry name

[Copilot]

CONTAINER1015 displayed an empty registry name because the RepositoryNotFound format string mapped {2} to the registry, but after adding baseImageDigest as a third argument, {2} became the digest and the registry name shifted to unused position {3}.

Changes

• Strings.resx: Updated RepositoryNotFound format string to include digest at {2} and registry at {3}, matching the existing call sites in ContainerBuilder.cs and CreateNewImage.cs
• XLF files: Regenerated all 13 localization files via /t:UpdateXlf

Before:

CONTAINER1015: Unable to access the repository '{0}' at tag '{1}' in the registry '{2}'...

After:

CONTAINER1015: Unable to access the repository '{0}' at tag '{1}' (digest: '{2}') in the registry '{3}'...

Original prompt

---

This section details on the original issue you should resolve

<issue_title>CONTAINER1015 does not contain the registry name</issue_title>
<issue_description>### Describe the bug
Instead of the registry name, the CONTAINER1015 message only shows an empty string.

To Reproduce

1. Use ContainerBaseImage with an unknown image
2. Check the error message

Further technical details

This was introduced with 6eeea6c and affects the following builds:

• 9.0.103+
• 9.0.200+
• 9.0.300+
• 10.0.100-preview.1+

Strings.RepositoryNotFound expects the repository name to be {2} but due to the change it's now {3}. {2} is now the base image digest instead.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes CONTAINER1015 does not contain the registry name #49083

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.