Please address the comments from this code review:

## Overall Comments
- When a container name from `ContainerStatuses` or the pod spec is not found in `containersByName`/`specContainersByName` the code silently continues; consider at least a debug log in these branches to aid diagnosing unexpected name mismatches between deployment and pods.
- The comment above `containersByName` has a small formatting issue (`//present`); fixing this improves readability and keeps comments consistent with the rest of the file.

## Individual Comments

### Comment 1
<location path="sensor/kubernetes/listener/resources/convert.go" line_range="334" />
<code_context>
+			specContainersByName[sc.Name] = sc
+		}
+
+		for _, c := range p.Status.ContainerStatuses {
+			deployContainer, found := containersByName[c.Name]
+			if !found {
</code_context>
<issue_to_address>
**suggestion:** Consider surfacing mismatches between deployment/spec containers and status containers instead of silently skipping.

Right now, missing entries in `containersByName` or `specContainersByName` are just skipped with `continue`, which hides cases where the deployment spec and pod status diverge (e.g., renamed, init, ephemeral, or partially failed containers). Consider at least a debug log in these branches, and ideally treat known container types (init/ephemeral) differently from truly unexpected container names so mismatches are visible during diagnosis.

Suggested implementation:

```golang
		// Build a map from container name to pod spec container for name-based lookup.
		specContainersByName := make(map[string]v1.Container, len(p.Spec.Containers))
		for _, sc := range p.Spec.Containers {
			specContainersByName[sc.Name] = sc
		}

		for _, c := range p.Status.ContainerStatuses {
			deployContainer, found := containersByName[c.Name]
			if !found {
				// Surface mismatches between deployment containers and pod status containers.
				// These can indicate renamed or unexpected containers and are useful for diagnosis.
				log.Debugf("Pod %s/%s: skipping status container %q with no matching container in deployment spec; this may indicate a renamed or unexpected container",
					p.GetNamespace(), p.GetName(), c.Name)
				continue
			}

			image := deployContainer.GetImage()

			var runtimeImageName *storage.ImageName
			if features.UnqualifiedSearchRegistries.Enabled() && c.ImageID != "" {
				continue
			}

```

1. Ensure this file has access to a `log` logger consistent with the rest of the package, for example:
   ```go
   var (
   	log = logging.LoggerForModule()
   )
   ```
   and that `github.com/stackrox/rox/pkg/logging` (or the appropriate logging package used elsewhere in this directory) is imported.
2. In the corresponding code paths where `specContainersByName` is used and a status container is not found for a spec container (likely another `if !found { continue }` branch when iterating spec containers), add a similar `Debugf` log. For spec containers, the message should emphasize that a container defined in the pod spec has no corresponding status entry, and explicitly mention if it is an init or ephemeral container when you have that context (e.g. when iterating over `p.Spec.InitContainers` or `p.Spec.EphemeralContainers` and their respective status slices).
</issue_to_address>