Update coco.yaml

[ADII877]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Added a new class label "guns" to the COCO dataset configuration file.

📊 Key Changes

• Included "guns" as a new class label (index 80) in the coco.yaml file.

🎯 Purpose & Impact

• 🆕 Expands the COCO dataset to support detection of "guns," enabling more specific object detection tasks.
• 🔧 Enhances flexibility for users working on safety, security, or related applications.
• 📈 Potentially improves model performance for datasets or projects requiring this additional class.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I sign the CLA

---

1 out of 2 committers have signed the CLA.
✅ (UltralyticsAssistant)[https://github.com/UltralyticsAssistant]
❌ @ADII877
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[UltralyticsAssistant]

👋 Hello @ADII877, thank you for submitting an ultralytics/yolov5 🚀 PR! To ensure a seamless integration of your work, please review the following checklist:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/yolov5 main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

Additionally, for a change like introducing a new class label in the COCO dataset configuration, here are some extra details to consider:

1. Reproducibility: Ensure you provide a minimum reproducible example (MRE) if required, such as a small sample dataset or script to showcase how this new label integrates with existing functionality.
2. Backward Compatibility: Please confirm that adding the new label does not conflict with current YOLOv5 training scripts, datasets, or detection models.
3. Documentation: Since this expands the dataset, kindly update the corresponding COCO and dataset-specific documentation (e.g., DATA.md) if needed.

For more guidance, please refer to our Contributing Guide. Don’t hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

This is an automated response. An Ultralytics engineer will review your PR and provide additional feedback soon. 😊