Wrap PR and discussion titles in toJSON to escape them in Slack

[AetherUnbound]

Fixes

Fixes an issue where quotes in a PR title would cause the Slack messaging to fail. This is due to the way the formatting was changed in #3577.

Example: https://github.com/WordPress/openverse/actions/runs/7616428574/job/20743158171?pr=3689

Description

GitHub Actions Expressions do not allow string substitution, only concatenation and formatting¹. Thus there's no easy way to replace the single or double quote characters in a PR title when interpolating them into the payload body. I am hoping that toJSON will appropriately escape those characters, but I have no idea if this will work!

Testing Instructions

Merge and find out, maybe?

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Footnotes

1. https://docs.github.com/en/actions/learn-github-actions/expressions#functions ↩

[dhruvkb]

LGTM! Hope it works.

[stacimc]

🤞