Fix incorrect reply associations in client database

[eloquence]

As noted in #1148, we have a production issue where replies are wrongly associated with a UUID instead of an ID as the foreign key. This has not caused any issues yet since we do not currently display reply authorship, but will cause issues for pilot users the moment we introduce reply badges.

We should consider a DB migration or other strategy for ensuring that data in production databases is corrected, if possible.

[eloquence]

(Since this is closely related to ongoing reply badges work, pulling into current sprint.)

[eloquence]

Marked as release blocker since we should be careful to release from main to production users until we have a migration in place for incorrect historical data.