The unsupported operations aren't saved in Redux, but it's still beneficial to use the same approach because it's more consistent, allows easier modification in the future (if we decide to keep all the operations in the DB, and avoids introducing a new mechanism.

https://linear.app/comm/issue/ENG-10329/create-a-new-action-and-modify-the-reducedmoperationsqueue-reducer

Depends on D14453

Tested the whole stack on both native and web:

1. Run the app on Redux version 86 with a modification to processDMOperation making all the INBOUND messages unsupported
2. On one platform created a thread and sent a text message. These were visible on the sender, and invisible on the recipient
3. Closed the recipient and added a migration that unshimms the thread creation operations, e.g.

unshimDMOperations(
  state,
  dmOperationTypes.CREATE_THREAD,
  handleReduxMigrationFailure,
): MigrationFunction<WebNavInfo, AppState>),

4. Run the recipient and noticed the thread appearing
5. Added another migration, this time unshimming text messages
6. Run the recipient and noticed messages appearing