Updating package release to run through the ESRP release pipeline

[scbedd]

Resolves #28160

This PR enables the usage of ESRP Release task for publish to PyPI. SDK Devs don't need to worry about this update, as the release process remains the same.

This PR:

• Updates our release process to use the ESRP Release task instead of twine upload using our azure-sdk account.
• On pypi, these packages will be published by the Microsoft account instead of the azure-sdk account.
• Not reflected in PR, but I also proved out the update to our partner drops pipeline.

Check doc/esrp_release.md for additional detail on break glass scenarios.

[scbedd]

I also need to adjust this PR to allow the partner release pipeline to use this same strategy. That commit will be added before merge after all the releases have finished up.

[scbedd]

Commenting old PR body for posterity.

@hallipr @JimSuplizio I basically copy-pasta-ed your configuration from sdk-for-java.

Excepting:

• Targeting PyPI instead of Maven
• Using Publisher ESRPRELTEST instead of ESRPRELPACMANTEST as that is what was used in the demo provided to me.

Any gotchas that I should be aware of other than actually running this thing?

EDIT: according to filed icm the ESRP team does not currently support uploading a tar.gz formatted sdist. PR is pending until they support it.

Further EDIT: 3/6/2023 ESRP team got back to me, re-ran the release, zip sdist is present now.