Run docs gh-pages publish outside Docker

[JacobSzwejbka]

Summary:

• Run the docs gh-pages publish script on the host instead of inside Docker.
• Keep using actions/checkout persisted credentials for the GITHUB_TOKEN-backed push.

Failure fixed:

• Post-Fix docs gh-pages publish authentication #20890 docs publish jobs still fail at git push -f with fatal: could not read Username for https://github.com: terminal prompts disabled because the Dockerized script cannot see checkout credentials from the host.

Testing:

• git diff --check
• Ruby YAML parse of .github/workflows/doc-build.yml

Notes:

• actionlint is not installed in this local environment.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/20896

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• Jobs not running on PR and it gets green to be landed without signals

❌ 2 New Failures, 1 Unrelated Failure

As of commit 931a6fd with merge base 28ebd34 ():

NEW FAILURES - The following jobs have failed:

• pull / unittest / linux / linux-job (gh)
  examples/models/test/test_export.py::ExportTest::test_efficient_sam_export_to_executorch
• pull / unittest-editable / linux / linux-job (gh)
  examples/models/test/test_export.py::ExportTest::test_efficient_sam_export_to_executorch

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / unittest-nxp-neutron / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.