Feature Request: Add a unified hook for tracking onchain action status across components

### Describe the solution you'd like

OnchainKit actions often move through several states such as preparing, awaiting signature, submitting, pending confirmation, and completed. Today, developers usually need to stitch together multiple signals from hooks or callbacks to track this lifecycle consistently.

### Problem Description
Without a unified way to observe action status, developers may duplicate logic across components or end up with slightly different interpretations of the same action state. This can lead to inconsistent UI behavior, duplicated loading indicators, and harder-to-maintain code.
Developers should be able to rely on a single, well-defined source of truth that represents the current status of an onchain action throughout its lifecycle.

### Describe alternatives you've considered.
Introduce a first-class hook (for example, `useOnchainActionStatus`) that exposes a normalized action state and relevant metadata, allowing components to react consistently to progress, success, or failure without reimplementing state logic.

Start by reviewing the existing OnchainKit hooks and callbacks that expose action lifecycle signals. Define the normalized statuses and metadata the proposed hook should provide, then verify that components can consistently observe progress, success, and failure through one source of truth.

Written by the indexing model from the issue text.