chore: release docs update plus auto publish docs site

[caseyisonit]

Description

• Updates the RELEASE_PROCESS.md doc with notes from the last release.
• Includes some improvements to auto-publish the doc site when the docs commit type merges into main
• Corrects a label in the auto-update action to watch for ready-for-review.
• PR template improvements since this is the first one using it.

Motivation and context

• The release process is now fully documented, including prerequisites, so anyone can get set up and do a release
• Docs site publishing regularly is a massive low-hanging fruit improvement for our consumers. This will now ensure accessibility doc improvements are shipping quickly and providing value instantly.
• @castastrophe introduced a super cool action a while ago, and I noticed the label was incorrect. This will now help keep branches up to date with the main that are ready for review.
• Better PR drafting experience

Related issue(s)

• NA

---

Author's checklist

• I have read the CONTRIBUTING and PULL_REQUESTS documents.
• I have reviewed at the Accessibility Practices for this feature, see: Aria Practices
• I have added automated tests to cover my changes.
• I have included a well-written changeset if my change needs to be published.
• I have included updated documentation if my change required it.

---

Reviewer's checklist

Manual review test cases

• Read the RELEASE_PROCESS.md and make sure it reads clearly

[changeset-bot]

⚠️ No Changeset found

Latest commit: fc46d68

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Branch preview

• Documentation Site
• Storybook

Review the following VRT differences

When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:

• Spectrum | Light | Medium | LTR
• Spectrum | Dark | Large | RTL
• Express | Light | Medium | LTR
• Express | Dark | Large | RTL
• Spectrum-two | Light | Medium | LTR
• Spectrum-two | Dark | Large | RTL
• High Contrast Mode | Medium | LTR

If the changes are expected, update the current_golden_images_cache hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.

[caseyisonit]

this is the label we use in swc repo, @castastrophe let me know if I'm misunderstanding the word label here :)

[blunteshwar]

nit
what will happen with this change?

[castastrophe]

Yeah, that makes sense to me. That utility will auto-rebase PRs with either of those labels present.

[castastrophe]

Honestly the utility can be a bit aggressive when used so I generally suggest a separate flag for it like "auto-update" to make sure you're opting into it specifically.

[caseyisonit]

@castastrophe should we change the label and update our PR docs to include a section about updating base?

[caseyisonit]

would love to better understand what you mean when you say "aggressive", maybe we sync in slack or huddle?

[github-actions]

Tachometer results

Currently, no packages are changed by this PR...

[castastrophe]

This looks so great! One nit, if there's only 1 item in the list, we can probably just list it without the indent.

[blunteshwar]

Great work!
Lets go!:rocket:

[caseyisonit]

the smoke test isnt working because my branch name is too long, was verified in #5439