Add type for train arguments

[RizwanMunawar]

@glenn-jocher Hi, this PR adds type annotations for each train argument. We already have the types for the predict, export, and track arguments, but train was missing until now. Thank you!

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Documentation updates improve clarity and accuracy across object counting, region counting, and argument descriptions in Ultralytics YOLO guides.

📊 Key Changes

• 🔧 Renamed Object Counter to ObjectCounter and Region Counter to RegionCounter for consistency in code examples within object and region counting guides.
• 📝 Enhanced table formats in predict-args.md and train-args.md:
  • Added explicit data types to columns for argument definitions.
  • Improved alignment and readability of default values and descriptions.

🎯 Purpose & Impact

• 🎯 Clarity: Improved terminology consistency in the guides ensures easier understanding and usage for users following the documentation.
• 📖 Readability: Enhanced formatting in argument descriptions aids quick reference and comprehension for developers configuring models.
• 🛠️ Developer Usability: Streamlined examples and clear naming reduce potential errors when implementing code snippets from the guides.

These changes make Ultralytics documentation more user-friendly and precise, benefiting both beginners and advanced users. 🚀

[UltralyticsAssistant]

👋 Hello @RizwanMunawar, thank you for submitting an ultralytics/ultralytics 🚀 PR! 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/ultralytics 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.
• ✅ 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! 🚀

This is an automated response, but rest assured, an Ultralytics engineer will review your request soon. 😊

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.97%. Comparing base (0fb6788) to head (986ed5c).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #18221      +/-   ##
==========================================
- Coverage   73.97%   73.97%   -0.01%     
==========================================
  Files         128      128              
  Lines       17138    17138              
==========================================
- Hits        12678    12677       -1     
- Misses       4460     4461       +1     

Flag	Coverage Δ
Benchmarks	35.00% <ø> (ø)
GPU	38.47% <ø> (ø)
Tests	67.76% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[glenn-jocher]

@RizwanMunawar great improvement! Can you check the other main tables and add missing types to those also if applicable?