Improve load time of transaction history with asynchronous programming

[IsaacCheng9]

Summary

• Currently, transaction history is loaded on demand in a synchronous manner.
• This means that the load time quickly becomes significant when the user has recorded a few transactions.
• Refactor the display of transaction history with asynchronous programming to address this.

[IsaacCheng9]

I've investigated potential implementations for this but I couldn't get a working solution after a few hours of trying. I think we should prioritise other things first and return to this later.