build(deps): update ultralytics requirement from >=8.3 to >=8.4.115 in /apps/ai

[dependabot]

Updates the requirements on ultralytics to permit the latest version.

Release notes

Sourced from ultralytics's releases.

v8.4.115 - Deprecate HUB in favor of Ultralytics Platform (#25608)

🌟 Summary

v8.4.115 transitions Ultralytics from legacy HUB integrations to the streamlined Ultralytics Platform experience, with simpler authentication and a leaner training codebase. 🚀

📊 Key Changes

• 🔐 Introduced validated Platform CLI authentication

  • Log in with yolo login API_KEY
  • Remove credentials with yolo logout
  • API keys are checked against the Platform before being saved.

• 🔄 Added settings migration to schema 0.0.7

  • Existing compatible settings, such as custom dataset and run directories, are preserved.
  • Legacy HUB configuration and incompatible HUB API keys are removed automatically.
  • Users with old credentials are directed to create a Platform API key.

• 🧹 Removed the legacy ultralytics.hub package

  • HUB authentication, remote training sessions, model loading, exports, dataset utilities, callbacks, and HUB-specific exceptions have been retired.
  • HUB-related API references, documentation pages, navigation entries, and the HUB example notebook were also removed.

• 🧠 Simplified model and trainer workflows

  • Models no longer load directly from HUB URLs.
  • Training no longer manages HUB sessions, remote checkpoints, heartbeats, or HUB-specific training arguments.
  • Platform callbacks remain available for streaming training information.

• 📚 Updated documentation and examples

  • Guides, notebooks, CLI help, and API documentation now reference the Ultralytics Platform instead of HUB.
  • Platform authentication and login commands are included in the quickstart and CLI documentation.

• ✅ Expanded test coverage

  • Added tests for settings migration, API-key validation, login, and logout behavior.

🎯 Purpose & Impact

• ✨ A clearer user experience: Platform is now the primary destination for dataset management, training, and deployment, avoiding confusion between HUB and Platform services.
• ⚡ Simpler authentication: The new yolo login command validates credentials directly and provides a more intuitive alternative to manually editing settings.
• 🛠️ Cleaner and easier-to-maintain code: Removing obsolete HUB components reduces dependencies, integration complexity, and potential maintenance issues.
• 🔒 Safer upgrades: Existing user settings are migrated instead of being reset, while outdated or incompatible HUB keys are discarded.
• ⚠️ Compatibility consideration: Applications that import ultralytics.hub, use HUB training sessions, load models from HUB URLs, or rely on HUB-specific utilities must migrate to Ultralytics Platform workflows.
• 🚀 Recommended next step: Create a Platform API key and authenticate with:

yolo login YOUR_API_KEY

For no-code dataset annotation, training, and deployment, use the Ultralytics Platform.

What's Changed

• Deprecate HUB in favor of Ultralytics Platform by @​sergiuwaxmann in ultralytics/ultralytics#25608

... (truncated)

Commits

• 98a9cfd Deprecate HUB in favor of Ultralytics Platform (#25608)
• ee3fe3e Surface Platform error messages and stop the console-output retry loop (#25581)
• 5c99019 Fix TorchScript GPU inference device mismatch (#25569)
• 16d89ef fix Python syntax error in similarity-search solution (#25579)
• 74ee4ac Document depth loss gains and attribute semantic and depth in the argument ta...
• a41b69b Fix DDP error when total batch size is higher than validation images (#25576)
• 5954e8e Fix NCNN and Paddle export of prompt-free YOLOE models (#25568)
• 37b64d0 Fix: Analytics line chart total_counts resets before update_graph consumes it...
• 56afc74 Fix Annotator.kpts() dropping keypoints and limbs on image borders (#25565)
• f338491 Fix IndexError in class_activation_map with out-of-range classes (#25582)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}