This PR removes the redundant GCP download bucket for weights files. This leaves the GitHub release assets as the sole source of weights, which while less robust is also easier to maintain, as I do not need to update two sets of weights on each release.

I believe the geographic issues we encountered before (i.e. downloading weights in China from Google Drive) should be a non-issue now with the GitHub-hosted weights.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Minor code refactor and error handling improvements in the YOLOv5 codebase.

📊 Key Changes

• Commented-out plotting call in test.py now refers to the updated module location utils.plots rather than utils.general.
• Import statement in autoanchor.py is adjusted to import directly from its own module.
• A new flag redundant is introduced in google_utils.py to handle a secondary download location in case the primary fails.

🎯 Purpose & Impact

• Ensures that when plotting is re-enabled in the future, it calls the correct function location, which helps in maintainability. 🛠️
• Improves code clarity in autoanchor.py by using a direct module reference, making it clearer where functions are coming from. 🧭
• The change in google_utils.py helps users by providing a fallback download option, ensuring that model weights can still be acquired even if the primary source fails. This enhances the reliability of the download process. 🔄🔗

Potential impact includes:

• Developers will have less confusion when maintaining or enabling plotting functionalities. 🖊️
• Users may notice improved error messages and fallback options in case of download issues, easing the setup process. 📥