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

Enhanced license formatting for improved clarity and consistency across the repo.

📊 Key Changes

• Updated license headers in several files to a clearer and more standardized format.
  • Changed "Ultralytics YOLO 🚀, AGPL-3.0 license" to "Ultralytics 🚀 AGPL-3.0 License - https://ultralytics.com/license".
• Updated comments in format.yml, .pre-commit-hooks.yaml, and pyproject.toml files for consistency.

🎯 Purpose & Impact

• 🧹 Improved consistency: Ensures that the license header is consistent across all files, making it easier to reference and understand.
• 📜 Clarity: Directs users to the license link for more detailed information.
• 🛠️ Minimal impact on functionality: No functional changes; this is purely an improvement in documentation and formatting for readability.

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting a PR to ultralytics/pre-commit 🚀! To ensure a smooth integration of your contribution, please review the following guidelines:

• ✅ Define a Purpose: Ensure your PR description clearly explains the intent of your changes. If applicable, link to any related issues to provide additional context. Commit messages should also be clear and follow our conventions.
• ✅ Synchronize with Source: Make sure your PR is up-to-date with the latest ultralytics/pre-commit main branch. If necessary, synchronize your branch by clicking the 'Update branch' button or running git pull followed by git merge main locally.
• ✅ Ensure CI Checks Pass: Check that all Continuous Integration (CI) systems pass successfully. Address any issues if they arise to ensure the PR is in a healthy state.
• ✅ Update Documentation: If your PR includes changes requiring updated documentation, make sure to revise the relevant docs.
• ✅ Add Tests: Add or update any necessary tests to verify your changes. Confirm that all tests complete successfully.
• ✅ Sign the CLA: Please confirm that you’ve signed our Contributor License Agreement (CLA) by commenting "I have read the CLA Document and I sign the CLA" if this is your first contribution to Ultralytics.
• ✅ Focus on Minimum Scope: Restrict your changes to the minimum scope needed for the update or fix. As Bruce Lee said, “Hack away the unessential.” 😄

For detailed guidance, refer to our Contributing Guide. Your PR title and description look informative, and the changes seem focused on improving license clarity and consistency—thank you for that! 🙌 However, if additional clarifications, tests, or updates are required from your end, we will let you know.

An Ultralytics engineer will review your PR soon and provide further feedback if needed. If you have any immediate questions, please feel free to ask here. Thanks again for your contribution to the Ultralytics community! 🌟

[UltralyticsAssistant]

🎉 The PR is officially merged—thank you @pderrenger and @glenn-jocher for your collaborative efforts! 🙌 Your work to polish and standardize the license formatting across the repo adds a layer of clarity and professionalism that truly elevates our project.

As Leonardo da Vinci once said, "Simplicity is the ultimate sophistication." Your contributions may seem subtle, but their impact is profound—making it easier for others to engage, learn, and build confidently with Ultralytics. 🚀

Keep shining and innovating—we deeply appreciate your dedication! ✨