Feature: Multi-Chain Transaction Data Table

[kamescg]

Context

The Universal Dashboard doesn't currently include a historical transaction view.

We need a minimal multi-chain transaction history data table to support a production alpha release.

We don't need to include asset changes updates (for now) in the data table, but we should prioritize adding an optimized and cost-efficient method for including that information when fetching transaction history.

Scope

Create a new transaction data table that represents a user's transaction history across multiple chains.

The multi-chain transaction history data fetching should occur in the api-universal application. Limiting the number of network requests required by the application frontend.

A new page should be added at the /transactions route and a menu item labeled "Transactions" added to Dashboard menu list.