Update action.yml spelling skip list

[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

Enhanced spell-check exclusions for various file types in GitHub actions.

📊 Key Changes

• Expanded the spell-check ignore list to include additional file extensions like .npy, .data*, *.pnnx, __pycache__*, *.ico, *.jpg, *.png, *.mp4, and *.mov.
• Excluded additional directories such as /runs and /.git.
• Refined documentation exclusions by specifying .md files in certain docs directories.

🎯 Purpose & Impact

• Minimize False Positives: By ignoring more irrelevant file types, the spell-check process is streamlined, reducing noise from false positives.
• Improve CI Efficiency: This will speed up the continuous integration process, making it quicker and more efficient as it avoids checking file types and directories that don't contain relevant content for spelling checks.
• Reduce Developer Distraction: Developers can focus on actual code and documentation typos rather than sorting through irrelevant spell-check results.

👩‍💻👨‍💻 Users can expect cleaner spell-check results, leading to a more efficient development workflow.