feat(provide_stat): add new page for provide stat

[ChayanDass]

Summary

This PR adds a new DHT Provide diagnostics screen to the IPFS WebUI, providing a graphical view of
ipfs provide stat data for the DHT Sweep provider (enabled by default in Kubo v0.39+).

The screen gives node operators a clear overview of:

• Reprovide cycle progress
• Current batch and queue status
• Worker utilization
• Network health and throughput
• Capacity warnings

This makes it possible to monitor DHT provide health without relying on the CLI.

---

Key Features

• New Diagnostics → DHT Provide screen
• Visualize cycle progress with ETA
• Current batch and queue metrics
• Worker utilization (periodic vs on-demand)
• Network connectivity and success rate
• Auto-refresh (60s) with manual refresh
• Graceful handling of unsupported Kubo versions
• UI built using reusable Card components (WebUI style)

---

Screenshots

Initial DHT Provide Screen

---

Technical Details

Data Source

• RPC endpoint: POST /api/v0/provide/stat
• Accessed via ipfs.provide.stat() through context (ProvideProvider)

Architecture

• New ProvideStat context for data fetching and refresh lifecycle
• UI composed of small, focused components:
  • ReprovideCycle
  • CurrentBatch
  • QueueStatus
  • Workers
  • Network
• Uses local Card primitives

---

next

• More detailed warnings and recommendations
• Tooltips for metrics
• Historical trend visualization

---

Checklist

• UI follows existing WebUI conventions
• No breaking changes
• Handles unsupported Kubo versions
• Screenshots included

[welcome]

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions
  and stakeholders linked/mentioned.

• Your contribution itself is clear (code comments, self-review for the
  rest) and in its best form. Follow the code contribution
  guidelines
  if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

• A maintainer will triage and assign priority to this PR, commenting on
  any missing things and potentially assigning a reviewer for high
  priority items.

• The PR gets reviews, discussed and approvals as needed.

• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!