feat: include target path hash in generated file names to prevent naming collisions

[ShantKhatri]

Description

This PR updates the host filename generation logic in convertFilesIntoVolumes() to ensure strict uniqueness for injected container files.

Previously, the host filename was generated using only the workload name and the file's basename (%s-files-%s). This PR updates the format to include both the container name and an 8-character SHA-256 hash of the full target path: fmt.Sprintf("%s-%s-files-%s-%s", workloadName, containerName, hash[:8], filepath.Base(target))

All associated tests have been updated to expect this new filename format.

What does this PR do?

This change is required because the previous logic caused two severe silent overwrite bugs on the host filesystem:

1. Intra-container collision: If a single container mounted /etc/app/config.yaml and /opt/app/config.yaml, the identical basenames caused them to resolve to the same host filename and silently overwrite each other.
2. Cross-container collision: If a web container and a worker container both mounted a file to /etc/config.yaml, the absence of the container name in the host filename caused them to silently overwrite each other.

By combining the container name and the path hash, we guarantee that no two file mounts will ever generate the same host filename, while keeping the basename visible for human readability when debugging.

Fixes #506

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• New chore (expected functionality to be implemented)

Checklist:

• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• I've signed off with an email address that matches the commit author.

[ShantKhatri]

Hi @mathieu-benoit @chris-stephenson , I wanna mention that previously, if two different containers (e.g., web and worker) in the same workload mounted a file to the exact same target path (e.g., /etc/config.yaml), their host files would silently overwrite each other because the container name was excluded from the filename generation.

By injecting both the containerName and the target path hash (%s-%s-files-%s-%s), this PR guarantees strict uniqueness for both intra-container and cross-container file mounts. Happy to hear any feedback or suggestions on this!

Note: This PR also fixes a related cross-container collision bug.