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

Adds Ultralytics' 🚀 AGPL-3.0 license headers to multiple project files for compliance and transparency.

📊 Key Changes

• Introduced license headers at the top of key Python files (detect.py, models.py, utils/datasets.py, utils/utils.py).
• Standardized alignment across the project by referencing the Ultralytics' AGPL-3.0 license URL.

🎯 Purpose & Impact

• Purpose: Ensures legal compliance by clarifying the usage and distribution rights of the code under the AGPL-3.0 license.
• Impact: Promotes transparency and proper attribution for Ultralytics projects, helping users understand their rights and obligations under the license. No impact on functionality 🚀.

[UltralyticsAssistant]

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

📌 Additional Notes

For efficient processing of your PR, please ensure that the changes align with the repository's conventions and that unnecessary modifications are avoided where possible. If this PR fixes a bug, please provide a detailed description of the issue and include a Minimum Reproducible Example (MRE) if not already provided so our team can better evaluate the fix.

For more guidance, please refer to our Contributing Guide. Don’t hesitate to leave a comment if you have questions or need clarification. An Ultralytics team member will review and assist you soon. Thank you for being a part of the Ultralytics community! 🚀

[UltralyticsAssistant]

🎉 The PR is merged! Huge thanks to @pderrenger for this thoughtful contribution and to @glenn-jocher for the collaboration! 🌟 Your work on adding AGPL-3.0 license headers ensures transparency and sets an inspiring standard for open-source excellence. 💪

As Marcus Aurelius once said, "What we do now echoes in eternity." This addition will not only safeguard our work but also empower the global community by fostering clarity and trust. Keep rocking 🚀, you’re making a lasting impact! 🙌