Add daily pipeline to register unregistered azure-mgmt-* package names

[msyyc]

What

Adds a new scheduled pipeline eng/pipelines/register-package-name.yml that runs daily to automatically register unregistered azure-mgmt-* package names on PyPI.

How it works

1. Scan: Finds all sdk/*/azure-mgmt-*/**/_version.py files where VERSION = "1.0.0b1" (new, unreleased packages)
2. Check PyPI: Queries PyPI for each candidate - skips packages already registered
3. Trigger: Calls pipeline 8013 (name reservation) via REST API with NameForReservation parameter for each unregistered package

Details

• Scheduled daily at 8:00 AM UTC
• No PR or push triggers
• Continues on error and reports all failures at the end
• Uses `` for pipeline-to-pipeline authentication

Test

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5950914&view=results, it found the unregistered package then trigger the namespace reserve pipeline automatically : https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5950943&view=results

[Copilot]

Pull request overview

Adds a new scheduled Azure DevOps pipeline to automatically detect newly introduced azure-mgmt-* packages that haven’t been registered on PyPI yet and trigger the existing name-reservation pipeline to reserve those package names.

Changes:

• Introduces a daily scheduled pipeline with no PR/push triggers.
• Scans sdk/*/azure-mgmt-*/**/_version.py for VERSION = "1.0.0b1" candidates.
• Checks PyPI registration status and queues pipeline 8013 for unregistered names.

[weshaggard]

We should use our 1ES hosted pool

[scbedd]

I see what you're going for here, but I think this is overly complex.

1. You can update the existing build to do the grep of the version files if there is no value for the package name for reservation. (make default value auto for the package name, which should trigger an additional grep for package name step). Doing it this way means you don't need to worry about access token to queue another build or anything like that. You can just add a schedule to the reserve-namespace-build as it is.
2. This issue covers the proper solution to this. I reached out to Mariana when this came up before. I KNOW we trigger a couple pipelines for this. That is the true solution to the issue that this PR is solving.

I'll approve a stop gap that just adds a scheduled run to the existing build.

[scbedd]

The single comment. I'm fine with just working this as a scheduled part of the existing namereserve build.