docs: Add note about manually using the `bump_patch_version` action (#10862)

Marshall Bowers created 

This PR updates the releases docs to make a note about
`bump_patch_version` action through the GitHub UI.

Not all of us have `gh` (or `brew`) installed.

Release Notes:

- N/A

Change summary

docs/src/developing_zed__releases.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)

Detailed changes

docs/src/developing_zed__releases.md 🔗 

@@ -33,9 +33,11 @@ If your PR fixes a panic or a crash, you should cherry-pick it to the current st
 You will need write access to the Zed repository to do this:
 
 - Send a PR containing your change to `main` as normal.
-- Leave a comment on the PR `/cherry-pick v0.XXX.x`. Once your PR is merged, the Github bot will send a PR to the branch.
+- Leave a comment on the PR `/cherry-pick v0.XXX.x`. Once your PR is merged, the GitHub bot will send a PR to the branch.
   - In case of a merge conflict, you will have to cherry-pick manually and push the change to the `v0.XXX.x` branch.
 - After the commits are cherry-picked onto the branch, run `./script/trigger-release {preview|stable}`. This will bump the version numbers, create a new release tag, and kick off a release build.
+  - This can also be run from the [GitHub Actions UI](https://github.com/zed-industries/zed/actions/workflows/bump_patch_version.yml):
+    ![](https://github.com/zed-industries/zed/assets/1486634/9e31ae95-09e1-4c7f-9591-944f4f5b63ea)
 - Wait for the builds to appear at https://github.com/zed-industries/zed/releases (typically takes around 30 minutes)
 - Proof-read and edit the release notes as needed.
 - Download the artifacts for each release and test that you can run them locally.