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 GitHub workflow files to enhance clarity and formatting consistency. 🚀

📊 Key Changes

• Improved license text formatting for clarity in three GitHub workflow files (cla.yml, format.yml, tag.yml).
• Added explicit references and links to the Ultralytics AGPL-3.0 License.

🎯 Purpose & Impact

• 🖇️ Enhanced Transparency: Clear and consistent license information highlights compliance and accessibility for contributors.
• 📋 Improved Documentation: Makes files easier to read and understand for developers and contributors.
• 🛠️ No Functional Changes: This update does not impact app functionality but maintains clean and professional workflows.

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting a ultralytics/yolo-ios-app 🚀 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/yolo-ios-app 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 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! 🚀

🌟 Summary

Thank you for providing a clear description and standardized license header updates for the project! 🚀

If this PR is addressing a particular issue, kindly ensure to link it in the description for traceability. Additionally, please verify that these changes do not conflict with any local workflows or project dependencies.

An Ultralytics engineer will review your submission soon and provide detailed feedback if needed. 😊 Your effort in contributing to the project's improvement is greatly appreciated!

[UltralyticsAssistant]

🎉 PR Merged! Huge thanks to @pderrenger for the thoughtful updates and @glenn-jocher for the collaboration on this one! Your attention to detail in enhancing clarity and consistency in our workflows is truly appreciated. 🚀

As Marcus Aurelius once said, "What stands in the way becomes the way." By refining even the smallest aspects of our workflows, you've helped smooth the path for contributors, making our community stronger and more accessible. Your work matters, and we're grateful! 💙 #Teamwork