Implement animation disable mechanism for instrumentation tests

[temcguir]

Problem

Continuous animations (like screen flash, focus pulse, audio amplitude) keep the Compose runtime busy, causing Espresso's idle checks to fail or time out on slow emulators.

Solution

Implemented a LocalDisableAnimations CompositionLocal to provide a flag to disable or snap animations.

• Provided from MainActivity based on an intent extra.
• Set in UiTestUtil via TestStorage arguments passed from the build configuration.
• Updated various components to respect this local and snap animations or use fixed states.

Impact

Drastically reduces CPU load and Espresso timeouts by stopping background animations during tests.

[gemini-code-assist]

Code Review

This pull request introduces a mechanism to disable animations within the application, primarily for testing purposes. It adds a LocalDisableAnimations CompositionLocal, updates MainActivity to read a disable_animations flag from TestStorage or an intent extra, and modifies various UI components to bypass animations when this flag is active. The review feedback focuses on making the implementation more idiomatic to Jetpack Compose by using conditional transitions within AnimatedVisibility and animateFloatAsState instead of manual if-else blocks, which reduces code duplication and nesting.

[temcguir]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces a mechanism to disable animations during tests by adding a LocalDisableAnimations CompositionLocal and passing a KEY_DISABLE_ANIMATIONS extra through the MainActivity intent. This flag is then used across various UI components to bypass or snap animations. The review feedback suggests replacing an arbitrary delay(50) in ScreenFlashOverlay with yield() to prevent test flakiness, and using EnterTransition.None instead of fadeIn(animationSpec = snap()) in LockSwitchCaptureButtonNucleus for architectural consistency.

[Kimblebee]

can get rid of this todo