MGMT plane release builds fail with contact and approver values

[danieljurek]

Workaround: Use a manual build to release packages

Example logs: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6658672&view=logs&j=88454c3d-6e95-5adc-4a41-ce24f9cc5124&t=8f8225ff-4f9a-5af5-4618-66c36da30b08&s=1e60b8b3-2cd6-59d1-321a-e91394b1f73c

Config Values Populated successfully. 

Validation of configManager.config instance failed. 

Execution failed with error :- 

owners is null 

approvers is null 

Possible solution: Populate information in the pipeline based on a statically defined fallback email address

                        - template: /eng/pipelines/templates/steps/esrp-publish.yml
                          parameters:
                            targetFolder: "$(Pipeline.Workspace)/esrp-release/${{parameters.ArtifactName}}/${{artifact.name}}"
                            ${{ if in(variables['Build.Reason'], 'IndividualCI', 'BatchedCI') }}:
                              owners: alias@microsoft.com
                              approvers: alias@microsoft.com

[msyyc]

FYI: since the failed pipeline already created release tag, we have to manually delete the release tag in https://github.com/Azure/azure-sdk-for-python/releases for target SDK then manually trigger release pipeline again.

[msyyc]

Now this issue blocks auto release for all Python Mgmt sdk, so we hope the issue could be fixed as soon as possible.

NOTE: more detains in teams channel