Update links.yml to remove --require-https

[glenn-jocher]

Thank you 🙏 for your contribution to Ultralytics 🚀! Your effort in enhancing our repositories is greatly appreciated. To streamline the process and assist us in integrating your Pull Request (PR) effectively, please follow these steps:

1. Check for Existing Contributions: Before submitting, kindly explore existing PRs to ensure your contribution is unique and complementary.

2. Link Related Issues: If your PR addresses an open issue, please link it in your submission. This helps us better understand the context and impact of your contribution.

3. Elaborate Your Changes: Clearly articulate the purpose of your PR. Whether it's a bug fix or a new feature, a detailed description aids in a smoother integration process.

4. Ultralytics Contributor License Agreement (CLA): To uphold the quality and integrity of our project, we require all contributors to sign the CLA. Please confirm your agreement by commenting below:

   I have read the CLA Document and I hereby sign the CLA

For more detailed guidance and best practices on contributing, refer to our ✅ Contributing Guide. Your adherence to these guidelines ensures a faster and more effective review process.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Update to link-checking workflow in Ultralytics documentation repository.

📊 Key Changes

• Removed the --require-https flag from the lychee link checker configuration.

🎯 Purpose & Impact

• 🌐 The purpose is to improve the link validation process by not strictly requiring HTTPS for all checked URLs.
• 🔗 This may reduce false-positive error rates for link checking, especially for URLs that may not enforce HTTPS but are still reachable and valid.
• 👥 For users and developers, this change aims to reduce confusion and maintenance work related to fixing or investigating broken link errors that aren't actually broken.