Repo tagging creates a tag with incorrect version - Release pipeline

[MilenaHristova]

Linked issue: https://github.com/dotnet/release/issues/666

Repo tagging for installer creates a tag with incorrect version. Investigation is described in the linked issue comment

[MilenaHristova]

There is a bug in repo-tagging.ps1 script where a asset is not found by name in manifest.json even though it exists. That happens because $manifestRepo.assets | Where { $_.name -eq $versionAssetName } returns a single object instead of a array and the subsequent check $asset.Count -gt 0 returns false and indicates that the asset is not found
Link to code.

[MilenaHristova]

there is a operation in ReleaseCli that does the same thing as the script https://dev.azure.com/dnceng/internal/_git/dotnet-release?path=/src/Microsoft.DotNet.Release/Microsoft.DotNet.ReleaseCli/src/Operations/CreateReleaseTagsOperation.cs&version=GBmain&_a=contents , we should consider using that instead