Bug

Fixes: https://github.com/NuGet/Client.Engineering/issues/3483

Description

There were several places our CI scripts look like it would either fail, or produce incorrect results, when a branch name has a slash (for example release/7.x). This PR tries to fix all of them.

• The OptProf pipeline was failing on the release/* branch, because the runsettings drop name was wrong. Fixed the build pipeline to publish it to the expected name
• ConfigureVstsBuild.ps1 writes the branch name to BuildInfo.json, and it was writing a branch name that doesn't exist.
• When publishing to BAR, we were telling it a branch name that doesn't exist.
• Our init steps of the build were tagging the builds with the commit author name and branch name. I don't believe these tags are useful, so I'm removing them. The branch name in particular is already visible in the Azure Pipelines GUI.
• Changing the OneLocBuild branch name. I don't know much about this process, but considering the input name is MirrorBranch, it feels to me like it should match the full name, not the substring after the last /.
• I'm changing where the product gets published, so I'll need to update the release pipeline and all servicing branches with this change.

PR Checklist

• Meaningful title, helpful description and a linked NuGet/Home issue
• Added tests N/A
• Link to an issue or pull request to update docs if this PR changes settings, environment variables, new feature, etc. N/A