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

Added consistent licensing headers across multiple project files for better clarity and compliance. 🛡️

📊 Key Changes

• Updated licensing headers with a clear format referencing the AGPL-3.0 License and its URL (e.g., https://ultralytics.com/license) across key files (e.g., workflows, metadata, pubspec.yaml, etc.).
• Applied the update to both main project files and example assets/code.

🎯 Purpose & Impact

• Purpose: Ensures uniform and visible licensing information throughout the project, reinforcing clear compliance with AGPL-3.0 requirements. 📝
• Impact: Provides developers and users with immediate transparency about the license terms, reducing confusion and promoting proper usage. Enhances professional documentation consistency across the repository. 🌐

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting a yolo-flutter-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 yolo-flutter-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! 🌟💻

🛠️ Notes About This PR

We see that your PR is focused on standardizing license headers across YAML and related configuration files. This is an important contribution to ensure compliance with licensing and project consistency! If you've missed any relevant files or need assistance, feel free to leave a comment.

📝 Please double-check:

1. If any additional files (e.g., hidden or ignored YAML files) need license updates.
2. That all files respect the formatting requirements in the project guidelines.

🤖 Automated Message

This response was generated automatically, but please rest assured, an Ultralytics engineer will review your PR in detail and assist you further soon! Thank you for your contribution 🚀

[UltralyticsAssistant]

🎉 The PR is merged – amazing work, @pderrenger and @glenn-jocher! Your attention to detail in adding consistent licensing headers ensures clarity, compliance, and professionalism throughout the project. 🛡️✨

As Marcus Aurelius once wrote, "What we do now echoes in eternity." Your contributions may seem procedural, but their impact—on developers, users, and our shared open-source mission—is profound and lasting. Thank you for making a difference! 🚀