perf: blazingly fast

[gomesalexandre]

Description

Attempt 1 at redux perf. improvements

Issue (if applicable)

• contributes to Spike data storage mechanisms for client side performance #7769

Risk

High Risk PRs Require 2 approvals

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

High - touches state. Getting this wrong could brick state, and we'd have to revert this and do a nuke of the whole state.

Testing

• Ensure app state still looks good
• Ensure rehydration (i.e refresh with persisted state) is still happy

Engineering

• ^
• Migrations are still happy
  NOTE: Ensure you check for slice state after rehydration (i.e {rehydrated: true} for the slice/s you're migrating) to ensure redux-persist rehydrated with your migration:
  
  

Operations

• 🏁 My feature is behind a flag and doesn't require operations testing (yet)

Screenshots (if applicable)

https://jam.dev/c/6fee8b7a-97d8-48b0-b420-b04f3ef008b4

[woodenfurniture]

Code wise very sane, will do second pass of runtime testing before giving final stamp

[0xApotheosis]

LGTM. Tested a couple of migrations and they worked as expected / properly rehydrated!

[NeOMakinG]

• Regeneration assets is properly creating a new line inside clearAssetsMigrations
• Assets migration seems to be working as expected
• Rehydration also seems to work as expected

I had a problem with the history of BTC but as seen in pm, it doesn't look linked with this PR

We have to take a lot of care with this PR because it will be pretty hard to revert if we push it to production, people would end in a borked state (I did try to come back to develop and I had to flush my cache to make it work)