Change Details

Test plan is to populate redux persist with threadActivity entries on a lower migration version and then upgrade the version. This migration will currently fail as is as there is a possible bug with redux persist thread activity not storing `lastPruned`. This is tracked by: https://linear.app/comm/issue/ENG-7663/missing-lastpruned-field-in-current-thread-activity-redux-persist By providing a default `lastPruned` value in the reducer, this migration works, but will need to fix ENG-7663 before landing. Will not land until test plan updated and issue resolved

Rebased to prior commit without threadActivity sqlite changes. Populated redux persist with thread activity entries via dispatch actions. Rebased back to current commits without migration. Encountered state difference due to missing migration. Ran the migration and previous entries are included in the sqlite database {F1549410}

Test plan is to populate redux persist with threadActivity entries on a lower migration version and then upgrade the version. This migration will currently fail as is as there is a possible bug with redux persist thread activity not storing `lastPruned`Rebased to prior commit without threadActivity sqlite changes. This is tracked by: https://linear.app/comm/issue/ENG-7663/missing-lastpruned-field-in-current-thread-activity-redux-persist By providing a default `lastPruned` value in the reducer,Populated redux persist with thread activity entries via dispatch actions. Rebased back to current commits without migration. this migration works,Encountered state difference due to missing migration. but will need to fix ENG-7663 before landing. Will not land until test plan updated and issue resolvedRan the migration and previous entries are included in the sqlite database {F1549410}