Small Updates to ESRP Process Doc (#33706)

* update the ESRP release process doc to account for escalation path.

Author: scbedd

doc/esrp_release.md

@@ -6,6 +6,10 @@ This process change should not affect the release process whatsoever. There will
 
 The primary visible effect of these release changes is that these packages will be published by the `Microsoft` pypi account, _not_  `azure-sdk` account that has been used until now.
 
+Further details on ESRP release methods is available at [docs.opensource.microsoft.com](https://docs.opensource.microsoft.com/releasing/publish-binaries/python/).
+
 ## Break Glass - Yanking/Deleting
 
-Contact the `python` team via email, teams, or ICM: `[email protected]`. Additionally [this document](https://docs.opensource.microsoft.com/releasing/publish-binaries/python/) is the official writeup on break glass scenarios.
+For low priority yank requests, directly contact the `python` team via email @ `[email protected]`. Ensure that the `package name`, the `version`, and the `yank reason` are readily available in the yank request email.
+
+If there is no response on the email, and the request is urgent. escalate to filing a sev 2 ICM. The process is documented [here](https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/1035/ESRP-Release-Task?anchor=escalating-to-esrp).