Use new Ultralytics Retry action

[pderrenger]

This Ultralytics PR refactors code to improve performance and readability. 🔄

Key changes include:

• 🚀 Optimized various functions for faster execution.
• 🧩 Simplified complex logic for better understanding and maintenance.
• 🗑️ Removed redundant code to streamline operations.
• 📚 Improved code structure and organization.

These changes aim to enhance the overall quality and efficiency of the code. 🌟

Learn more about Ultralytics:

• About Us 🌐
• Install the Ultralytics App 📲
• Read Our Blog 📝
• Learn about YOLO 🤖
• Explore Ultralytics HUB 🚀
• Check Out Our Plans 💼
• Join our Team 🌾
• AI in Healthcare 🏥
• AI in Manufacturing 🏭
• Attend YOLO VISION 2024 📅

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

This PR updates the workflow for link checking to improve reliability and maintainability by switching to a different GitHub Action.

📊 Key Changes

• Replaces nick-invision/retry@v3 with ultralytics/actions/retry@main for the retry mechanism in GitHub Actions workflows.
• Changes parameter names from retry_wait_seconds to retry_delay_seconds and max_attempts to retries.

🎯 Purpose & Impact

• Consistency: By using an in-house action (ultralytics/actions/retry@main), the workflow aligns better with the rest of the repository's ecosystem, which could improve consistency in maintenance.
• Reliability: The update might address any previous reliability issues experienced with link checking by leveraging a more tailored retry solution.
• Simplified Maintenance: Maintaining control over the retry mechanism can lead to more efficient workflow management as changes or customizations are easier to implement. 🚀

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting an ultralytics/yolov5 🚀 PR! This is an automated response to help guide you through our process, and an Ultralytics engineer will assist you soon.

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/yolov5 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.
• ✅ Provide a Minimum Reproducible Example (MRE): For bug reports, include a simple example that reproduces the issue you're addressing, if applicable.
• ✅ 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! 🚀