fix: update flows when screen is visible

[david-allison]

Purpose / Description

Knowing what I know now, repeatOnLifecycle(Lifecycle.State.STARTED) is better

Fixes

• Fixes Update flows when the screen is visible, but not interactive #19632
• Split out of Card Browser: Migrate to Material 3 SearchView #18709

Approach

• refactor to use context parameters
• Change State.RESUMED => State.STARTED

How Has This Been Tested?

Unit tests: 1 fixed - the Robolectric runBlocking workaround wasn't perfect

I went through all seemingly risky functionality using my Pixel 9 Pro - no catastrophic issues.

Learning (optional, can help others)

Robolectric isn't perfect

Cause:

• improvement: introduce DeckPickerViewModel #17690 (comment)
• => e35b5b9

Checklist

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner

[criticalAY]

One question rest is all good, will approve once its resolved

[criticalAY]

Just curious and want to know what will happen if the app is in background and value is updated (lets say) lastValue check will see the new value when the app resumes, compare it to the new value property, and potentially skip the UI update.