Replaced cURL slack workflows with slackapi

[The5cheduler]

Fixes

Fixes #3461 by @dhruvkb

Description

replaced the cURL with slackapi for github-actions to make it more aligned and maintainable.

Testing Instructions

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.

[sarayourfriend]

LGTM and thanks for the contribution! Can you run the linting (just lint) locally and commit the changes? That way this will pass CI and we'll be able to merge it.

[dhruvkb]

Thanks for the contribution and agree with @sarayourfriend about linting. Just wanted to bring your attention to the file you possibly missed: https://github.com/WordPress/openverse/blob/ca35fa5f23d05575e78774ddc9a58c1b671aca2a/.github/workflows/pr_limit_reminders.yml?

[obulat]

There should be a new line at the end of each file

[The5cheduler]

Thank you so much @obulat and @dhruvkb.
I got little busy with holidays so was not able to make changes you requested.
Thank you so much for applying changes on my behalf.

Best,
Pk Patel

[dhruvkb]

Thanks for the continue to collaborate on this @The5cheduler! The code needs some additional work to fix the errors. I've labelled them in 2 files but the changes will apply to all 3.

I'm sorry we focused more on fixing linting issues before actual problems.

[dhruvkb]

Here $msg is not defined. You can copy the message text from before and paste it here. Also the payload is regular YAML so the quote interpolations "'" are not needed here.

Suggested change

	{"user": "'"$slack_id"'","message": "'"$msg"'"}
	{
	"user": "${{ env.slack_id }}",
	"message": "<actual message from before>"
	}

Also the same note about environment variables as the other review comment.

[sarayourfriend]

Thanks for the contribution @The5cheduler 🙏 It all looks good except on significant but easy to miss detail about how GitHub Action variables work. I've left a comment explaining the required change, and then this should be good-to-go, I think 😁

[sarayourfriend]

Brilliant, thank you @The5cheduler 🎉

[openverse-bot]

Based on the low urgency of this PR, the following reviewers are being gently reminded to review this PR:

@obulat
@dhruvkb
This reminder is being automatically generated due to the urgency configuration.

Excluding weekend¹ days, this PR was ready for review 6 day(s) ago. PRs labelled with low urgency are expected to be reviewed within 5 weekday(s)².

@The5cheduler, if this PR is not ready for a review, please draft it to prevent reviewers from getting further unnecessary pings.

Footnotes

1. Specifically, Saturday and Sunday. ↩

2. For the purpose of these reminders we treat Monday - Friday as weekdays. Please note that the operation that generates these reminders runs at midnight UTC on Monday - Friday. This means that depending on your timezone, you may be pinged outside of the expected range. ↩

[krysal]

Fantastic, @The5cheduler. Thank you!

Review comments were addressed.