Update issues link on the about page

[zackkrida]

Fixes

Fixes #567 by @krysal

Description

Updates the "issue" link on the about page to point to the issues landing page. This is much clearer for users who do not already have a GitHub account or who aren't logged in.

Testing Instructions

Go to the /about page locally and click the "issue" link. Observe you are taken to the catalog issue list.

Checklist

• My pull request has a descriptive title
• 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.

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.

[dhruvkb]

Doesn't solve the problem but it's much better for the user than seeing a GitHub login screen without explanation. LGTM!

[zackkrida]

We do also suggest 'sending an email' after the suggestion to create a GitHub issue. Email should be accessible and low-tech enough for most people, I think.

[github-actions]

Playwright failure test results

It looks like some of the Playwright tests failed. You can download the Playwright trace
output for all playwright tests that have failed at the bottom of this page, under the
"Artifacts" section:

https://github.com/WordPress/openverse/actions/runs/4244082120

Read more about how to use this artifact here: https://github.com/WordPress/openverse/blob/main/frontend/test/playwright/README.md#debugging

[github-actions]

Playwright failure test results

It looks like some of the Playwright tests failed. You can download the Playwright trace
output for all playwright tests that have failed at the bottom of this page, under the
"Artifacts" section:

https://github.com/WordPress/openverse/actions/runs/4244082120

Read more about how to use this artifact here: https://github.com/WordPress/openverse/blob/main/frontend/test/playwright/README.md#debugging

[krysal]

We do also suggest 'sending an email' after the suggestion to create a GitHub issue. Email should be accessible and low-tech enough for most people, I think.

Yeah, thinking again, that seems sufficient for people not knowledgeable of GitHub and find the template for New Provider issues more valuable than linking to the GitHub issues page as well 😅 Perhaps we don't need to change anything here!