[EPIC] [Improvement] Self-service release issues after generating SDK

Currently, we apply the new [management sdk release process](https://microsoft-my.sharepoint.com/:w:/r/personal/prmarott_microsoft_com/_layouts/15/Doc.aspx?sourcedoc=%7B4238FE84-FC55-4B3D-A453-09291F93451C%7D&file=Management%20SDK%20release%20planner%20user%20guide.docx&action=default&mobileredirect=true&DefaultItemOpen=1&wdOrigin=EXCELONLINE.SHELL%2CAPPHOME-WEB.JUMPBACKIN&wdPreviousSession=948aba00-3bed-42cd-9853-b2470640675a&wdPreviousSessionSrc=AppHomeWeb&ct=1746687704719&share=IQGE_jhCVfw9S6RTCSkfk0UcAXuzXFnRMlO55KiSljSiy0c).

Azure sdk team is only responsible for service generate sdk, after that, it's service team's reponsibility to release sdk.
Unexpected issues may block service team to release sdk **after** sdk generated.
To **improve user experience** and **reduce manual fix** for self-service release, please add `sub-issues` for service teams when they have trouble on self-service release **after** Shanghai engineers generate SDK.

The goal of this issue is to:
- collect any issue that block service team to continue release process **after** shanghai sdk engineers generated sdk
- analyse the issue and improve releasing tools if possible

Start by reviewing the linked management SDK release process guide and the post-generation handoff described in this issue. Collect release blockers encountered by service teams after SDK generation, then analyse whether each needs a sub-issue or a release-tool improvement. Done means the blockers are documented with actionable follow-up work.

Written by the indexing model from the issue text.