rusk-wallet: Implement moonlight history

[Daksh14]

Closes #2271

[herr-seppia]

Would be possible to have a tx history containing both Phoenix and moonlight transactions?
Why did you split them?

Additionally (but not blockers):

• try to store the history in rocksdb to improve performance and unload archival computation (we already store Notes, you only miss the derived TransactionHistory objects)
• add a warning if the user is not connected to an archival

[Daksh14]

Would be possible to have a tx history containing both Phoenix and moonlight transactions?
Why did you split them?

Additionally (but not blockers):

• try to store the history in rocksdb to improve performance and unload archival computation (we already store Notes, you only miss the derived TransactionHistory objects)
• add a warning if the user is not connected to an archival

Mixing the moonlight and phoenix tx history would be confusing no? I can add another column that displays transaction type but that would add more info and make it harder to read

I split the history because all other methods are also split on public/private it makes sense.

Can you create issue for those two points you mentioned?

[Neotamandua]

Mixing the moonlight and phoenix tx history would be confusing no? I can add another column that displays transaction type but that would add more info and make it harder to read

In the long run, I think it is necessary to add such a column anyway. Because we want to differentiate between different types of transactions (transfer out, transfer in, conversion, deposit, withdrawal, etc.).

[herr-seppia]

Because we want to differentiate between different types of transactions (transfer out, transfer in, conversion, deposit, withdrawal, etc.).

These infos are already available in the transaction history in the "method" column IIRC

[Daksh14]

@herr-seppia I merged them both and made another PR for pagenation
@herr-seppia @Neotamandua