Support for NuGet Promotion

[sebastiengamby]

Is your feature request related to a problem? Please describe.
I need a NuGet promotion functionality similar to the one provided by ProGet

Describe the solution you'd like to see
When promoting a build that contains a NuGet artifact whose version number is a pre-release one (e.g. 1.2.4-RC-1), a new package is created than it is identical to the first with the exception of the version number that is a stable one (e.g. 1.2.4). This new package is placed in the target repository and when consulting the build details, it now appears in the related artifacts.

Describe alternatives you've considered
I have managed to address almost fully the issue with two scripts. The first one is a Powershell script executed by a build agent that

• Download the NuGet package to be promoted
• Unzip it
• Modify the nuspec file by editing the version number (e.g. 1.2.4-RC-1 to 1.2.4)
• Create a new NuGet package
• Upload the package
• Call the user plugin script
  The user plugin script does the following:
• Retrieve the detailedBuildRun
• Add the newly created package to the list of artifact of the module whose name matches the buildName
• Add the fileInfo of this newly created package to the list of artifactFiles of the detailedBuildRun
• Copy the VCS properties of the original package to the new one
• Add a release status to the buildRun
  This solution is almost correct because when consulting the details of the buildRun in the Artifactory UI, the newly created artifact is presented but the RepoPath link is undefined.
  nuget.groovy.txt

Additional context
I have added the scripts and a screenshot of the issue. This is also related to the JFROG support ticket 250742

promo.ps1.txt
nuget.groovy.txt