Rewrite publish-extension documentation for SDK cutover
Updated documentation for the publish-extension workflow now that the ext-sdk-bundle-rollout flag has reached 100% in stable releases. Corrected workflow behavior details including nightly release dispatch methods and stable release tagging sequence.
The ext-sdk-bundle-rollout flag reached 100%, so stable releases now ship a
standalone build of main through ext-vscode-publish-stable.yml rather than the
combined legacy+next A/B VSIX. Rewrite the skill around that path and record
what is left to retire.
Also corrects two things the old text got wrong: nightly is manual-dispatch
only (the cron was removed because PublishNightly gained required reviewers,
so unattended runs sat waiting and starved their successors), and the stable
workflow tags before it builds, so a tag-push failure fails early rather than
leaving a published-but-untagged release.
Source: original entry ↗