Feature Request: Add first-class transaction status polling hook with configurable confirmations

### Describe the solution you'd like

After submitting a transaction, applications typically need to:
- poll for transaction confirmation
- handle dropped or replaced transactions
- wait for a configurable number of confirmations
- surface intermediate states in the UI

## Expected Behavior
- Developers can track transaction lifecycle using a simple hook.
- Confirmation depth (e.g., 1, 2, N confirmations) is configurable.
- Hook handles common edge cases (dropped, replaced, timeout).

### Describe alternatives you've considered.

Proposed Solution

- Introduce a useTransactionStatus hook that:
- polls transaction receipt and block confirmations
- exposes standardized status values (pending, confirmed, failed, dropped)
- supports configurable confirmation depth and polling interval
- Detect and surface replaced or dropped transactions.
- Integrate cleanly with existing OnchainKit provider configuration.

No file or test is named. Start by reading the existing OnchainKit provider configuration and transaction-related hook entry points to understand current patterns. Done means a documented useTransactionStatus hook exposes pending, confirmed, failed, and dropped states, supports configurable confirmations and polling, and handles replacement and timeout cases.

Written by the indexing model from the issue text.