fix(docs-testimonial): Update Testimonial Addition Process

[ArvindParekh]

Fixes Issue

Closes #10055

Changes proposed

Updated the Testimonial addition process in the docs, now that the Add Testimonial button has been removed.
The new process now includes the following steps:

• Go to the Issues Tab
• Create a new Issue
• Select the type 🏆 Testimonial
• Fill in your testimonial

Check List (Check all the applicable boxes)

• My code follows the code style of this project.
• My change requires changes to the documentation.
• I have updated the documentation accordingly.
• All new and existing tests passed.
• This PR does not contain plagiarized content.
• The title of my pull request is a short description of the requested changes.

Screenshots

Before:

After:

Note to reviewers

[ArvindParekh]

Also, there's another image that may need updating:

This image is based on the fact that an issue with type "testimonial" has been created through the Add Testimonial button (and has a pre-populated field of user), which is not the case now. The new issue now will not have any pre-populated field.
Considering this, do you prefer that I update the image as well? It's a minor change, but we can do it for consistency. Let me know what you think.

[ThomasCode92]

As you suggested, I would update the image as well for consistency.
Upon approval of this PR, the documentation for adding testimonials will be accurate and complete.

[eddiejaoude]

Thank you 👍

[eddiejaoude]

Also, there's another image that may need updating:

This image is based on the fact that an issue with type "testimonial" has been created through the Add Testimonial button (and has a pre-populated field of user), which is not the case now. The new issue now will not have any pre-populated field. Considering this, do you prefer that I update the image as well? It's a minor change, but we can do it for consistency. Let me know what you think.

this can come in another issue/PR - having the pre-filled image I think it is good, it gives them an example, but the repo name is the previous (old) repo name, so it would be good to update. I will merge this PR so not to block the value it already adds to the users

[ArvindParekh]

Also, there's another image that may need updating:

This image is based on the fact that an issue with type "testimonial" has been created through the Add Testimonial button (and has a pre-populated field of user), which is not the case now. The new issue now will not have any pre-populated field. Considering this, do you prefer that I update the image as well? It's a minor change, but we can do it for consistency. Let me know what you think.

this can come in another issue/PR - having the pre-filled image I think it is good, it gives them an example, but the repo name is the previous (old) repo name, so it would be good to update. I will merge this PR so not to block the value it already adds to the users

I understand. I can update the image to reflect the new repo name, also pre-populating the name field.
Should I just directly raise a pr for that and reference this pr, or would you like me to create a new issue?

[eddiejaoude]

Please create an issue first