Update action.yml to ignore model files

[glenn-jocher]

@sersiossm ignores model files now!

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

Enhanced spelling checks in CI pipeline by refining ignored file patterns.

📊 Key Changes

• Expanded the --skip list in codespell to include additional machine learning model file extensions.
• Previously skipping *.csv, *.onnx, and *.pt files, the new pattern now excludes:
  • *.pth
  • *.torchscript
  • *.tflite
  • *.pb
  • *.bin
  • *.param
  • *.mlmodel
  • *.engine

🎯 Purpose & Impact

• Purpose: To prevent codespell from unnecessarily scanning binary or model-specific files, as these typically won't contain human-generated spelling errors that the tool is designed to catch.
• Impact: Users should see a cleaner and more relevant output from the spelling check step in the CI (Continuous Integration) process, reducing distractions from false positives and focusing attention on actual text-based code or documentation issues. This leads to more efficient code reviews and maintenance.