Add blog badge for object counting in zones topic

[RizwanMunawar]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Adds an Ultralytics Blog link to the “Track Objects in a Zone using Ultralytics YOLO” notebook across README and docs to improve learnability and navigation. 🧭✨

📊 Key Changes

• Inserted a new Ultralytics Blog badge/link in README for the "Track Objects in a Zone using Ultralytics YOLO" notebook.
  • Link: Region-based object counting using Ultralytics YOLO11 🔗
• Updated docs metadata (docs/notebooks-data.yml) to include the same blog link for consistent surfacing in site-generated pages.

🎯 Purpose & Impact

• Enhances user guidance with a complementary blog tutorial, making it easier to understand region-based counting workflows. 📚
• Improves discoverability and consistency across README and documentation pages. 🔍
• No code changes—zero impact on functionality or performance; purely documentation and UX improvement. ✅

[UltralyticsAssistant]

👋 Hello @RizwanMunawar, thank you for submitting an ultralytics/notebooks 🚀 PR! This is an automated response — an Ultralytics engineer will review and assist you soon. 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/notebooks 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
• ✅ Autogenerated Table Consistency: Since the README table is auto-generated by workflows/table.yml, please confirm your updates are reflected in docs/notebooks-data.yml (e.g., the new blog link for “Track Objects in a Zone using Ultralytics YOLO”) and that all existing entries/badges remain intact. 🧹🔗

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! 🚀📚

[RizwanMunawar]

@onuralpszr Hi, I think this one is missing your approval. Can you please take a look when you get some time? Thank you.