Docs: Update "Issues" section in the "Introduction to Contributing" chapter

[adiati98]

Description

Issues with "needs triage" label are not available to take until the label is removed. Our bot gives this information whenever someone use the .take command. However, this information is also worth to mention in the docs.

Suggested Solution

• Add information about it, change the format in this section to undordered list, and adjust some wording for better read and understanding.

Here is the copy:

## Issues

- If you wish to work on an open issue, please comment on the issue with `.take`, and it will be assigned to you.

  :::info
  
  If an issue is not assigned, it is assumed to be available for anyone to work on. Please assign yourself to an issue _before_ working on it to avoid conflicts.

  :::

- Issues with the `needs triage` label are unavailable to `.take` until they are triaged and the label is removed. Feel free to check on the issue regularly if you want to work on it.
- If you contribute to the project for the first time, you can search for issues with `good first issue` or `bug` labels in the repository. 
  
  :::note
  
  Please only self-assign a `good first issue` one time.

  :::

• Capitalize the "code of conduct" term in the last paragraph.

  - Please follow our [code of conduct](./code-of-conduct.md) in all your interactions with the project and its contributors.
  + Please follow our [Code of Conduct](./code-of-conduct.md) in all your interactions with the project and its contributors.

Code Blocks

Below are the code blocks that need to be changed:

docs/docs/contributing/introduction-to-contributing.md

Lines 29 to 38 in 83e4fbc

	## Issues
	If you wish to work on an open issue, please comment on the issue with `.take`, and it will be assigned to you. If an issue is not assigned, it is assumed to be available for anyone to work on. Please assign yourself to an issue before working on it to avoid conflicts.
	If you contribute to the project for the first time, you can search for issues with `good first issue` or `bug` labels in the repository. Please only self-assign a `good first issue` one time.
	In case you get stuck, feel free to ask for help in the [Discord](https://discord.gg/U2peSNf23P) server or [GitHub Discussions](https://github.com/orgs/open-sauced/discussions).
	Please follow our [code of conduct](./code-of-conduct.md) in all your interactions with the project and its contributors.

Note

• Please check each list whenever you fixed an item.
• Please move the checklists in your PR and check them when they are complete.

[HappyLife2]

.take

[github-actions]

Thanks for taking this on! If you have not already, join the conversation in our Discord

[adiati98]

Hey @HappyLife2,

Checking in here.
How is this going? Do you need any help?
I've updated the instructions in the issue to (hopefully) make it easier for you to understand.

Also, heads up. If there is no activity for this issue until the end of this week (Friday), we will unassign you and give this issue to other contributor to work on. 😊

Thank you!

[adiati98]

Hi @HappyLife2,

Because there is no response from you on this issue, as per informed on the last comment we unassign you from this issue.

Feel free to take it if you're still interested and when there is no one assigned to this issue.

Thank you. 😊

[smhussain5]

.take

(Will work on it today and let you know if there are any questions!)

[github-actions]

Thanks for taking this on! If you have not already, join the conversation in our Discord

[github-actions]

🎉 This issue has been resolved in version 1.66.1 🎉

The release is available on:

• GitHub release
• ghcr.io container (@latest dist-tag)

Your semantic-release bot 📦🚀