update migrations

ensure the connect farcaster prompt appears on second cold start

fix migration logic

need to finish testing this

make cold start count a per-alert type count instead of a global count, migrations, stagger the connect farcaster and community directory prompts

1. use coldStartCount to make sure we don't display connect farcaster alert right after NUX
2. use connectFarcasterAlertInfo in DisplayCommunityDirectoryPromptHandler to make sure we don't display community directory prompt until a day after connect farcaster prompt

the hardware back button on android does close the bottom sheet, but doesn't trigger the component's onChange callback

address feedback

Feels like there are probably ways to dismiss the modal without setting the fid to null here. Ideally we can catch all methods of closing the modal, but if that's really hard, one alternative would just be to set the fid to null as soon as we show the modal.

In D14444#401312, @ashoat wrote:

Does it not occur on every single login because the NUX doesn't display on subsequent logins?

Alternately, does this occur for every fresh install login?

Ended up testing the connect farcaster flow and it works. A couple things worth noting:

1. The connect farcaster bottom sheet appears at the same time as the NUX tips if the user installs the app and logs in. Not sure if this edge case is worth addressing

some updates

need to think about how to sequence things a little more

In D14378#399480, @ashoat wrote:

Can you share a screenshot of the order we end up seeing? Curious in what order the boosted communities will appear

CI has been stuck for a day

CI has been stuck for a day

address feedback

address feedback

reverted this change. reopening to reintroduce the change

Ah I accidentally landed an older version of this diff

address feedback