Standardize license headers in Python files

[pderrenger]

This PR updates all Python 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 Python files except those in venv

Learn more about Ultralytics licensing 📚

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

This PR adds license headers to multiple files across the project, ensuring compliance with software licensing requirements.

📊 Key Changes

• Added # Ultralytics 🚀 AGPL-3.0 License - https://ultralytics.com/license to the top of the following files:
  • wave_pytorch_gcp.py
  • train.py
  • train_tf.py
  • utils/torch_utils.py
  • utils/utils.py

🎯 Purpose & Impact

• Purpose: Ensures proper attribution and compliance with the AGPL-3.0 license terms.
• Impact: Maintains transparency and legal clarity, safeguarding Ultralytics’ intellectual property while making the licensing terms explicit for users and contributors. 🌐✅

[UltralyticsAssistant]

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

This is an automated response to your PR. An Ultralytics engineer will review your submission and provide additional feedback soon. Stay tuned! 😊

[UltralyticsAssistant]

🎉 This PR is officially merged—huge thanks to @pderrenger for leading the charge and to @glenn-jocher for your valued contributions! 🚀✨

By ensuring that every file reflects Ultralytics' AGPL-3.0 license, you've helped us strengthen not just our code but the principles of transparency and shared knowledge that bind our community. 🌍💡

As Marcus Aurelius once said, "What we do now echoes in eternity." Your work today safeguards our innovation and leaves a lasting impact on the open-source world. 🙌 Keep up the phenomenal contributions—together, we're building something extraordinary! 💪