Update Indexer to Support Transaction History Display Optimization

[sssning121]

Expected Behavior

In addition to subscribing to Confirm events, the scanner plugin should also subscribe to non-Confirm events (e.g., Request, Initiated, LimitChanged) to detect transactions at the time of submission and create a pending transaction record immediately, enabling real-time display.

Specifications

As a developer,I want to extend the scanner plugin’s event subscription logic so that we can detect transactions earlier—before confirmation—and immediately display them in the transaction history.

Features:

• Modify event subscription logic to include non-Confirm events

Development Tasks:

• Update the indexer's subscription rules to include non-Confirm events.