!14998 update issue instruction in mindSpore contributing guidelines

From: @clement_li
Reviewed-by: @zhunaipan,@zhoufeng54
Signed-off-by: @zhoufeng54

CONTRIBUTING.md

@@ -91,6 +91,7 @@ When reporting issues, refer to this format:
 
 - What version of env (mindspore, os, python etc) are you using?
 - Is this a BUG REPORT or FEATURE REQUEST?
+- What kind of issue is, add the labels to highlight it on the issue dashboard.
 - What happened?
 - What you expected to happen?
 - How to reproduce it?(as minimally and precisely as possible)
@@ -101,6 +102,7 @@ When reporting issues, refer to this format:
 - **If you find an unclosed issue, which is exactly what you are going to solve,** please put some comments on that issue to tell others you would be in charge of it.
 - **If an issue is opened for a while,** it's recommended for contributors to precheck before working on solving that issue.
 - **If you resolve an issue which is reported by yourself,** it's also required to let others know before closing that issue.
+- **If you want the issue to be responded as quickly as possible,** please try to label it, you can find kinds of labels on [Label List](https://gitee.com/mindspore/community/blob/master/sigs/dx/docs/labels.md)
 
 ### Propose PRs