[History] Consolidate Transfer and Staking History Storage

[0xkynz]

Issue Description

Currently, our Casper wallet stores transfer history and staking history in two separate local storage keys. This creates unnecessary complexity and increases the chances of data inconsistencies. This issue aims to improve the wallet by consolidating the storage of transfer and staking history into a single local storage key for a more efficient and reliable experience.

Current Behavior

Transfer history is saved in local storage under the key transaction_histories, and staking history is saved under the key staking_transaction_histories.

Desired Behavior

We want to merge the transfer and staking history into a single local storage key named transaction_histories. This will make it easier to manage and ensure that the data remains consistent and synchronized.

Steps to Reproduce

1. Open the CasperDash web wallet.
2. Navigate to the "Transfer History" tab.
3. Navigate to the "Staking History" tab.

Additional Context

This improvement will not only simplify the codebase but also enhance the user experience by reducing potential data discrepancies. It will make it easier for users to access their complete transaction history in one place.

Local Storage Keys

• Transfer History Key: transaction_histories
• Staking History Key: staking_transaction_histories

Proposed Solution

We propose refactoring the wallet to use a single key, transaction_histories, for both transfer and staking history. This will involve code changes in the storage and retrieval of transaction data.

Acceptance Criteria

• The Casper wallet should successfully store and retrieve both transfer and staking history using the new transaction_histories key.
• The user interface should be updated to reflect the changes and display all transaction history accurately.