Standardize license headers in TOML/YAML files

[pderrenger]

This PR updates all YAML file headers to use a standardized license format. 🔄

Changes:

• 📝 Standardized header: # Ultralytics 🚀 AGPL-3.0 License - https://ultralytics.com/license
• 🧹 Ensures consistent spacing after headers
• 🔍 Applies to all YAML files except those in venv

Learn more about Ultralytics licensing 📚

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Updated licensing references and added consistency in GitHub workflow files 🛠️✨.

📊 Key Changes

• Updated licensing comments in GitHub workflow files to maintain a consistent format:
  • Added "Ultralytics 🚀 AGPL-3.0 License - https://ultralytics.com/license" to dependabot.yml, format.yml, and stale.yml.
• No functional code changes were made.

🎯 Purpose & Impact

• 🔒 Improved License Clarity: Ensures clear visibility of the AGPL-3.0 license in workflow files, aiding compliance and transparency.
• 🧹 Consistency: Provides uniform documentation headers across files, improving maintainability and professionalism.
• No direct impact on users or code functionality but streamlines project management.

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting a ultralytics/xview-yolov3 🚀 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 if relevant, link to any associated issues. The more detail, the better!
• ✅ Synchronize with Source: Ensure your PR is synchronized with the ultralytics/xview-yolov3 main branch. If it's out of sync, update it by clicking the 'Update branch' button here on GitHub or by running git pull and git merge main locally.
• ✅ Verify CI Passes: Confirm all Ultralytics Continuous Integration (CI) checks are passing. CI failures may require updates to your code.
• ✅ Update Documentation: If applicable, update the relevant documentation to reflect any new or modified features in your PR.
• ✅ Add or Modify Tests: For any functional changes, include or revise tests to confirm your modifications work as expected. Ensure all tests pass!
• ✅ Sign the CLA: If this is your first contribution to Ultralytics, please sign our Contributor License Agreement (CLA) by commenting "I have read the CLA Document and I sign the CLA".
• ✅ Ensure Minimal Changes: Keep your code changes to the minimum essential for your updates. 🦾 "Simplicity is the soul of efficiency." – Austin Freeman

For additional guidance, refer to the Contributing Guide. If you've encountered a bug, consider providing a minimum reproducible example (MRE) to help us reproduce and debug the issue faster. 🚀

Thank you for contributing to Ultralytics! An Ultralytics engineer will review your PR shortly and provide further feedback. 😃

[UltralyticsAssistant]

🎉 Your PR has been merged—thank you, @pderrenger, with contributions from @glenn-jocher, for your attention to detail and commitment to excellence! ✨

The updated licensing references and workflow consistency may seem small, but as Aristotle wisely said, "Well begun is half done." These improvements lay a stronger foundation for clarity, professionalism, and future growth within the project.

Your contributions make a difference—keep building greatness, team! 🚀💡