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

Minor updates to repository metadata and workflow files for consistency and clarity.

📊 Key Changes

• Added the Ultralytics license notice to the GitHub workflow file (format.yml) and the repos.yaml file.

🎯 Purpose & Impact

• 📝 Ensures contributors and users are consistently reminded of the licensing terms, encouraging transparency.
• 🚀 Aligns metadata and documentation with Ultralytics' standards, improving overall project clarity and professionalism.

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting an ultralytics/stars 🚀 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/stars 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

For bug reports, if you haven’t already provided one, kindly include a Minimum Reproducible Example (MRE) to help us better understand and resolve the issue. MREs are essential for identifying root causes efficiently and can include code snippets, input data, or steps to replicate the behavior reliably.

For more guidance, please refer to our Contributing Guide. Don’t hesitate to leave a comment if you have any questions. An Ultralytics engineer will review your PR shortly and assist further. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🎉 This PR is now merged – thank you, @pderrenger, with contributions from @glenn-jocher, for leveling up our metadata and workflows with clarity and consistency! 🚀 Your attention to detail ensures Ultralytics remains professional, transparent, and welcoming to all.

As Marcus Aurelius once said, “What we do now echoes in eternity.” Your work today isn’t just about workflows—it’s about building a foundation that inspires collaboration and excellence for years to come. 💡❤️