[darc/maestro++] darc-add-build-to-channel command failing after the build promotion pipeline succeeds publishing assets

• This issue is blocking
• This issue is causing unreasonable pain users using this command to test things / add builds to channels after the fact are experiencing problems.

Got a few reports that darc fails the command after triggering and succeeding to run the build promotion pipeline that publishes the assets and attempts to add the build to the channel

 darc add-build-to-channel --id 46931 --source-branch master --source-sha c5358d4e1cc821f0b826a0eea75afd331aa2bbd0 --channel ".NET Core 3.1 Release"
Assigning the following build to channel '.NET Core 3.1 Release':
Repository: https://github.com/dotnet/test-templates
Branch: master
Commit: 2720fcade72d709a5d2fe80d0b80fbdac54213f6
Build Number: 20200326.1
Date Produced: 26/03/2020 17:49
Build Link: https://dev.azure.com/dnceng/internal/_build/results?buildId=574617
BAR Build Id: 46931
Released: False
Channels:
- .NET Core 5 Dev
Build 46931 will be assigned to channel '.NET Core 3.1 Release' once this build finishes publishing assets: https://dnceng.visualstudio.com/internal/_build/results?buildId=576519
Waiting '60' seconds for promotion build to complete.
Waiting '60' seconds for promotion build to complete.
Waiting '60' seconds for promotion build to complete.
Waiting '60' seconds for promotion build to complete.
Waiting '60' seconds for promotion build to complete.
The promotion build finished but the build isn't associated with the channel. This is an error scenario. Please contact @dnceng.

FYI @JohnTortugo

[riarenas]

I checked just in case, the build is still not in the channel 😦

[JohnTortugo]

I’m going to delete the ChannelReleasePipelines entries so we don’t trigger the release pipeline runner anymore and thus this shouldn’t happen again.

Talked with v-team and did the above.