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 standardize license formatting across workflow and project files. 🛠️✨

📊 Key Changes

• Adjusted the license formatting in format.yml, publish.yml, and pyproject.toml to a consistent style:
  Changed from Ultralytics YOLO 🚀, AGPL-3.0 license to Ultralytics 🚀 AGPL-3.0 License - https://ultralytics.com/license.

🎯 Purpose & Impact

• 📄 Improved Clarity: Ensures the license reference is standardized and easier to understand.
• ✅ Consistency: Promotes a polished, uniform format across all project-related files.
• 🌐 Transparency: Reinforces openness and accessibility by linking directly to the license details.

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting a ultralytics/thop 🚀 PR! To ensure a seamless integration of your changes, please review the following checklist:

• ✅ Define a Purpose: Clearly explain the purpose of your modifications in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and follow the project's conventions.
• ✅ Synchronize with Source: Verify your PR is synchronized with the ultralytics/thop main branch. If it's outdated, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Confirm all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please investigate and resolve them.
• ✅ Update Documentation: Ensure that relevant documentation is updated for any new or changed features.
• ✅ Add Tests: If applicable, include or update tests to validate your changes and ensure all tests are passing.
• ✅ Sign the CLA: If this is your first Ultralytics PR, please sign our Contributor License Agreement (CLA) by adding a comment saying "I have read the CLA Document and I sign the CLA".
• ✅ Minimize Changes: Keep your changes focused on the task at hand and aim for simplicity. Remember, "Simplicity is the soul of efficiency." 💡

If your PR addresses a bug, and you haven't already, we kindly request that you provide a minimum reproducible example (MRE) showing the issue. This will help us verify and incorporate your fix more efficiently.

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 and assist with your PR soon. Thank you for contributing to our open-source efforts! 🚀

[UltralyticsAssistant]

🎉 PR Merged! 🌟 Huge thanks to @pderrenger for leading this improvement and to @glenn-jocher for the insightful collaboration. Your dedication to standardizing the license formatting may seem like a small change, but it’s these thoughtful details that build trust, clarity, and a stronger foundation for the Ultralytics community. 🚀🔗

As Marcus Aurelius said, "Well-being is attained by little and little, and nevertheless is no little thing itself." Your contributions exemplify this principle—small yet impactful, fostering transparency and consistency for all. 💡✨ Thank you!