Fix(input focus): Bypass change detection in process_recorded_focus_changes

[kfc35]

Objective

• Fixes New FocusGained and FocusLost caused text cursor to stop blinking #23759
• Res<InputFocus> has is_changed() returning true every frame because process_recorded_focus_changes mutates it every frame now. Other systems that were relying on InputFocus.is_changed() for when the current_focus changes are no longer working as intended because of that change.

Solution

• Bypass change detection whenever ResMut<InputFocus> is accessed in process_recorded_focus_changes.

Testing

• cargo run --example feathers --features=“experimental_bevy_feathers”: text cursor now blinks correctly again
• cargo run --example directional_navigation verified via println! statement in update_focus_display that the system isn’t running on every frame (since it has a run condition .run_if(|input_focus: Res<InputFocus>| input_focus.is_changed()))

[github-actions]

Your PR caused a change in the graphical output of an example or rendering test. This might be intentional, but it could also mean that something broke!
You can review it at https://pixel-eagle.com/project/B04F67C0-C054-4A6F-92EC-F599FEC2FD1D?filter=PR-23765

If it's expected, please add the M-Deliberate-Rendering-Change label.

If this change seems unrelated to your PR, you can consider updating your PR to target the latest main branch, either by rebasing or merging main into it.

[kfc35]

Strange, there seems to have been an error uploading the screenshots and that’s why the pixel-eagle comment is there:
https://github.com/bevyengine/bevy/actions/runs/24297815059/job/70945786727
"jq: parse error: Invalid numeric literal at line 1, column 10”

Anyway, it can probably be ignored?

[alice-i-cecile]

Aha, that's why!