[Save-PSResource] Add the name of the primary module into the error message when a dependency does not exist

Summary of the new feature / enhancement

When a dependency does not exist, the error message does not specify the name of the primary module concerned :

If I specify several module names, I don't know which primary module is causing the problem.

Proposed technical implementation details (optional)

Add the name of the primary module into the error message.

Version :

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Binary     0.5.23     Microsoft.PowerShell.PSResourceGet  {Find-PSResource, Get-InstalledPSResource, Get-PSResourceRepository, Ge...

Key   : PSVersion
Value : 5.1.19041.3031
Name  : PSVersion


Key   : PSEdition
Value : Desktop
Name  : PSEdition


Key   : PSCompatibleVersions
Value : {1.0, 2.0, 3.0, 4.0, 5.0, 5.1.19041.3031}
Name  : PSCompatibleVersions


Key   : BuildVersion
Value : 10.0.19041.3031
Name  : BuildVersion


Key   : CLRVersion
Value : 4.0.30319.42000
Name  : CLRVersion


Key   : WSManStackVersion
Value : 3.0
Name  : WSManStackVersion


Key   : PSRemotingProtocolVersion
Value : 2.3
Name  : PSRemotingProtocolVersion


Key   : SerializationVersion
Value : 1.1.0.1
Name  : SerializationVersion

Reproduce Save-PSResource with several module names and a missing dependency, then trace the error path that produces the dependency message. Update the relevant message so it identifies the primary module involved, and verify that the output distinguishes which module failed when multiple modules are specified.