Standardize license headers in Python files

[glenn-jocher]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Updated license references in all project files by adding a URL link to the Ultralytics license for enhanced visibility and compliance. 🌐

📊 Key Changes

• Replaced the static license comment in each file header with a new format:
  "AGPL-3.0 License - https://ultralytics.com/license" 📜
• Updated headers in all relevant source code and test files to consistently include the new license link.

🎯 Purpose & Impact

• Purpose

  • Ensures users have direct access to the license details by linking to the official webpage.
  • Promotes clarity and transparency regarding licensing terms.

• Impact

  • No functional changes to the codebase, ensuring backward compatibility. ✅
  • Simplifies verification of licensing terms for developers and project contributors. 💼

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting an ultralytics/hub-sdk 🚀 PR! To ensure a seamless integration of your work, please review the following checklist:

• ✅ Define a Purpose: Clearly explain the purpose of your changes within the PR description. If applicable, link to any relevant issues for this enhancement or bug fix. Ensure your commit messages are clear and follow the repository's conventions.
• ✅ Synchronize with Source: Confirm your PR is up to date with the latest changes in the main branch of ultralytics/hub-sdk. If it’s outdated, please rebase or merge the latest changes by running git pull followed by git rebase or git merge main.
• ✅ Ensure CI Checks Pass: Make sure that all Continuous Integration (CI) checks associated with this PR are passing. Address any failing checks or tests.
• ✅ Update Documentation: If your changes affect the repository’s functionality, consider updating the documentation to reflect these updates.
• ✅ Add Tests: Include or revise tests within the repository to ensure thorough coverage of your changes, guaranteeing their reliability moving forward. Verify that all tests pass locally and in CI workflows.
• ✅ Sign the CLA: If this is your first contribution to Ultralytics, don’t forget to sign our Contributor License Agreement (CLA) by commenting "I have read the CLA Document and I sign the CLA" within this PR.
• ✅ Minimize Changes: Keep your modifications focused and limited to the purpose of the PR. Aim to “hack away the unessential” and streamline your updates to ensure efficient review and integration.

Next Steps 🚀

• Please double-check the PR description for clarity and comprehensiveness, ensuring reviewers can easily understand the proposed changes and their purpose.
• Follow the guidelines mentioned above to address any necessary updates. For more information, review our Contributing Guide.
• If you encounter any questions or require additional support, feel free to comment here. An Ultralytics engineer will assist you shortly.

Thank you for your contribution and for being part of the Ultralytics community! 🚀

[UltralyticsAssistant]

🎉 PR Merged! Thank you, @glenn-jocher, for your thoughtful updates to the license references—bridging clarity and accessibility in every file. 🌐 Your work ensures that our project's values and transparency are unmistakably present for all contributors and users. 👏

As Marcus Aurelius once said, "What we do now echoes in eternity." Your efforts here may seem small, but they shape a foundation of trust and integrity that will ripple through the open-source world. 💡

Thank you for making an impact! 🚀