Scripts downloaded using Save-Script do not have associated gallery metadata #535
Description
If you download a module using Save-Module, the module comes with a hidden xml file that contains metadata related to the gallery from which it was saved. This is useful when you want to identify where a certain module came from, even if it was xcopy-deployed to a system.
If you download a script using Save-Script, you just get the script file. There is no additional metadata related to the gallery from which the script was saved, so you cannot identify where that script came from if it was xcopy-deployed to a system. This differs from Install-Script, which creates an xml file in a InstalledScriptInfos folder where the script was installed.
It would be useful if the xml metadata for scripts was available when you invoke Save-Script as well, so that it could be copied along with the script to remote systems, with remote systems being able to identify where that script was copied.
It would also be useful if there was a Deploy-Module and a Deploy-Script command to deploy downloaded scripts to specific targets along with their metadata into the standard install-script location by default (but customizable via a parameter) so that users don't forget something, which may very well happen with an xcopy deploy of a script.