feat(deck-options): handle computeMemory progress

[david-allison]

Purpose / Description

We now show more information than just 'Processing'

Fixes

• Fixes Show progress when updating FSRS memory states #16642

Approach

• add logs to find the data in the proto
• handle computeMemory

How Has This Been Tested?

• Enable FSRS
• Save
• A computeMemory progress dialog is shown

Screen_recording_20260430_201904.webm

Learning (optional, can help others)

Out 'Amount' progress indicator abstraction isn't entirely correct. In computeMemory, we have a label, we do not want to format Amount as a string, but we do want to use it to display as progress in the dialog.

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

[user1823]

Next version

I realize that you want to avoid unintended bugs, but as I noted on the issue, most users won't even see the progress in the next version because it will be sped up by >10 times (10.18s → 853ms).

• Speed up update_memory_state by batching FSRS memory state calculation ankitects/anki#4335

So, you might want to consider including this in 2.24 if you feel that this is a low-risk change.

[david-allison]

I'd rather keep patch releases for patches rather than sneak functionality in.

@mikehardy FYI, open to disagreement. I'm hoping we get to 2.25 pretty quickly

[mikehardy]

Fewer people even having the potential to see actually means it's even lower priority- same risk of bugs and smaller benefits. We will hopefully do 2.25 quickly- 2.24 (and all its betas) built right off main so we're currently very stable