Fix pr-docs safe outputs checkout path

[IEvangelist]

Description

Follow-up to the pr-docs-check workflow after the v0.67.2 regeneration work.

Root cause

Run https://github.com/microsoft/aspire/actions/runs/24118533263 completed the agent phase and produced the docs changes, but create_pull_request still fell back to an issue-style comment on #15906 (comment).

The safe-outputs handler error was:

Repository 'microsoft/aspire.dev' not found in workspace. Make sure it's checked out using actions/checkout with a path.

So this was no longer a token/permission problem. The generated safe_outputs job was checking out microsoft/aspire.dev at the workspace root, but the cross-repo PR creation handler expects that target repo checkout to live under an explicit path.

What this changes

• Updates the generated safe_outputs job to check out microsoft/aspire.dev with path: aspire.dev.
• Runs the git remote configuration from that checkout via working-directory: aspire.dev.

Why this should work

The agent already had access to the docs repo and produced a valid create_pull_request output. This change aligns the follow-up safe-output job with the handler's workspace discovery requirement so it can actually open the draft PR instead of falling back to the explanatory comment.

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 15960

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 15960"

[Copilot]

Pull request overview

Updates the generated pr-docs-check safe-outputs job so the cross-repo PR creation handler can reliably discover the microsoft/aspire.dev checkout in the workflow workspace, avoiding fallback to issue-style comments.

Changes:

• Check out microsoft/aspire.dev under an explicit path: aspire.dev in the safe_outputs job.
• Run the git remote/token configuration step from working-directory: aspire.dev.

[github-actions]

Re-running the failed jobs in the CI workflow for this pull request because 1 job was identified as retry-safe transient failures in the CI run attempt.
GitHub was asked to rerun all failed jobs for that attempt, and the rerun is being tracked in the rerun attempt.
The job links below point to the failed attempt jobs that matched the retry-safe transient failure rules.

• Tests / Hosting-1 / Hosting-1 (windows-latest) - Job-level runner or infrastructure failure matched the transient allowlist.