update DEEP_FUTURE date to deep future date

[achen2401]

As reported by Anna, the Time Since Reply column is showing identical erroneous text due to default deep future date, i.e. 2025-01-01 is now in the past. (see code references here and here).

screenshots of issue:

[mcjustin]

Thanks Amy, your change makes sense to me. Odd that we only had it at 2025 earlier... @pbugni do you recall why?

[pbugni]

Thanks Amy, your change makes sense to me. Odd that we only had it at 2025 earlier... @pbugni do you recall why?

I do not. Certainly wasn't very deep in the future...

[mcjustin]

@achen2401 , Anna asked today "for the bug with the "time since last reply" column, will we need to manually clear that date for each participant? If so, is there a way for your team to do so in a bulk action?"

Does this change need a corresponding migration?

[achen2401]

@mcjustin sorry, I didn’t think this through, but I believe we do need a corresponding migration to address existing patient records with the not future date.

[mcjustin]

@mcjustin sorry, I didn’t think this through, but I believe we do need a corresponding migration to address existing patient records with the not future date.

@pbugni can you please take this migration on? It is a lower priority than the truenth issue.

(For my reference, we have used this capacity recently: #78 )