feat: more automated awesome-ipfs PRs

What kind of PR is this?

Select only one to speed up review/approval; i.e., don't lump an addition and a removal into a single PR.

[N/A] Adding something new to awesome-ipfs
[N/A] Editing something already listed on awesome-ipfs
[N/A] Removing something from awesome-ipfs
[x] Something else (if so, please explain in the "Additional details" section below)

Please confirm ALL of the following before submitting your PR.

[N/A] This PR includes only one addition, removal, or edit.
[N/A] I edited the /data directory instead of the README.md.
[x] I reviewed the content policy and the and the IPFS Community Code of Conduct to ensure my submission meets the requirements.
[x] I have followed the CONTRIBUTING.md guidelines.

This PR is a part of addressing concerns raised in #420 and elsewhere, and adds the following features:

Automatically update README.md for users. All they need to do to contribute is modify the data/** files.
Runs awesome_bot via github actions instead of via circleci
Posts comment to PRs giving insight into what was changed.
- If .github/** was changed, a regular message will be displayed.
- If data/** was changed
  - A message will be displayed indicating the YAML data has been edited.
  - If there are broken links, danger-js will fail the PR
- If src/** was changed, a warning will be displayed
- If scripts/** was changed, a warning will be displayed

See https://github.com/SgtPooki/awesome-ipfs/pull/2 for an example of what these changes do. You can look at the edit history for https://github.com/SgtPooki/awesome-ipfs/pull/2#issuecomment-1246145056 to see the different types of messages.