Remove redundant ComputeLoss code

[zhiqwang]

Because ComputeLoss does not inherit from other classes.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Improvement in loss computation in Ultralytics' YOLOv5 model.

📊 Key Changes

• Removed the unnecessary super() call from the ComputeLoss class constructor.

🎯 Purpose & Impact

• Purpose: The PR seems to streamline the loss class by eliminating a redundant superclass initialization, which wasn't required.
• Impact: This change might slightly improve the initialization performance of the ComputeLoss class and reduce potential confusion about inheritance hierarchy for developers working with the codebase.
• User Benefit: Users of YOLOv5 will likely not notice any direct changes, but developers can experience a cleaner and potentially less error-prone codebase. 🛠️✨

[github-actions]

👋 Hello @zhiqwang, thank you for submitting a 🚀 PR! To allow your work to be integrated as seamlessly as possible, we advise you to:

• ✅ Verify your PR is up-to-date with origin/master. If your PR is behind origin/master an automatic GitHub actions rebase may be attempted by including the /rebase command in a comment body, or by running the following code, replacing 'feature' with the name of your local branch:

git remote add upstream https://github.com/ultralytics/yolov5.git
git fetch upstream
git checkout feature  # <----- replace 'feature' with local branch name
git rebase upstream/master
git push -u origin -f

• ✅ Verify all Continuous Integration (CI) checks are passing.
• ✅ Reduce changes to the absolute minimum required 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

[glenn-jocher]

@zhiqwang PR is merged. Thank you for your contributions to YOLOv5 🚀 and Vision AI ⭐