Add section about issue labels to CONTRIBUTING.md (Azure#2620)

* Initial plan for issue

* Add section about issue labels to CONTRIBUTING.md

Co-authored-by: RickWinter <[email protected]>

* Address PR feedback on CONTRIBUTING.md issue labels section

Co-authored-by: heaths <[email protected]>

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: RickWinter <[email protected]>
Co-authored-by: heaths <[email protected]>

Author: 3 people

CONTRIBUTING.md

@@ -8,6 +8,17 @@
 
 - (Recommended) If you use [Visual Studio Code], install recommended extensions to improve your development experience.
 
+## Finding Issues to Work On
+
+If you'd like to contribute to the Azure SDK for Rust, we recommend looking for issues with the following labels:
+
+
+- [good first issue](https://github.com/Azure/azure-sdk-for-rust/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) - These issues are a good starting point for new contributors since they should be relatively straightforward to address.
+
+- [help wanted](https://github.com/Azure/azure-sdk-for-rust/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) - These issues are areas where we're actively seeking community contributions.
+
+Further discussion on or pull requests for these issues is highly valued, and we encourage you to participate in the discussions or take on the tasks described in these issues.
+
 ## Generated code
 
 If you want to contribute to a file that is generated (the file is located in a `generated` subdirectory), the best approach is to open a PR on the TypeSpec specification since we cannot replace generated code that will be replaced when regenerated.