feat: toggle auto advance in new reviewer

[RobozinhoD]

it also changes the behavior to match the desktop code, so auto advance only starts after the user toggles it

Fixes

• Fixes part of Auto-Advance active automatically #17701

How Has This Been Tested?

Nothing.webm

more.webm

Checklist

Please, go through these checks before submitting the PR.

• 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

[BrayanDSO]

LGTM. I'm okay with using the desktop approach of only start auto advance after it is enabled.

I'm also okay with to enable it by default, which feels more natural and practical, but I'm not strong enough about it to diverge from the desktop version.

Anyway, this is a developer option and it is not worth to block it because of that. Changing it takes only 30 seconds, and discussions sometimes take 30 days.

Furthermore, there are a lot of scenarios related to auto advance. Some @NeedsTest would be nice

[mikehardy]

also LGTM, I prefer not to deviate from desktop at all personally so wouldn't do so here

not sure where I'd concretely suggest a NeedsTest except everywhere which is then not really specific and matches rest of code base