Update Actions with Lychee and GitHub Token

[pderrenger]

This pull request adds an improved Ultralytics Actions workflow to automatically format code and documentation to the new Ultralytics official standards maintained at https://github.com/ultralytics/actions.

Five individual actions are run by default now including a new broken links check for markdown and HTML files. Disable individual actions by setting them to false or removing their line, i.e. delete 'markdown: true' line to disable markdown formatting.

To customize an action use a pyproject.toml file in this repo. For details see https://github.com/ultralytics/actions.

# Ultralytics 🚀 - AGPL-3.0 license
# Ultralytics Actions https://github.com/ultralytics/actions
# This workflow automatically formats code and documentation in PRs to official Ultralytics standards

name: Ultralytics Actions

on:
  push:
    branches: [main]
  pull_request_target:
    branches: [main]

jobs:
  format:
    runs-on: ubuntu-latest
    steps:
      - name: Run Ultralytics Formatting
        uses: ultralytics/actions@main
        with:
          token: ${{ secrets.GITHUB_TOKEN }}  # automatically generated
          python: true
          docstrings: true
          markdown: true
          spelling: true
          links: true

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

WARNING ⚠️ this PR is very large, summary may not cover all changes.

🌟 Summary

Improved code readability and maintainability by refactoring across multiple Python files.

📊 Key Changes

• 🧹 Cleaned up imports, removing unused ones.
• ⚙️ Standardized formatting for consistency, like adding spaces and breaking long lines.
• 🛠️ Replaced single letter variables with more descriptive names.
• 📝 Added docstrings to functions and classes.
• 🚀 Optimized performance with minor algorithm improvements.
• 💡 Added more inline comments for clarity.
• 🔗 Corrected and updated URLs and import paths.
• 🐛 Fixed bugs related to variable scope and type mismatches.

🎯 Purpose & Impact

• The changes aim to enhance code readability, making it easier for developers and contributors to understand and modify the code.
• Increased maintainability facilitates future updates and potential bug fixes.
• Performance optimizations may lead to faster execution and improved resource utilization.
• The updates contribute to an overall healthier codebase that aligns with best practices.