[AVM CI Environment Issue]: Publishing validation not checking for child-module

### Check for previous/existing GitHub issues

- [x] I have checked for previous/existing GitHub issues

### Issue Type?

Bug

### Description

It appears the child-module publishing works, but its validation does not. As the example of the storage-account file share shows ([ref](https://github.com/Azure/bicep-registry-modules/actions/runs/16381388275/job/46294338009#step:4:338)), the validation that runs in a step after the publishing checks for the top-level storage account module as opposed to the file-share child.

Potential areas the issue could reside:
- The wrong value is returned by the publishing function
- The wrong value is passed to the validation step in the workflow
- The validation step does not run for the correct module / does not run for a loop of module (if any)