Catch camera error states and display CameraErrorDialog in PreviewLayout

[davidjiagoogle]

Summary

• Define CameraError in :core:model and add cameraError: CameraError? to CameraState in :core:camera.
• Catch CameraX StateError codes (ERROR_CAMERA_IN_USE, ERROR_MAX_CAMERAS_IN_USE, ERROR_OTHER_RECOVERABLE_ERROR, ERROR_STREAM_CONFIG, ERROR_CAMERA_DISABLED disambiguated via DevicePolicyManager.getCameraDisabled, ERROR_CAMERA_FATAL_ERROR, ERROR_DO_NOT_DISTURB_MODE_ENABLED, ERROR_CAMERA_REMOVED), synchronous IllegalArgumentException from bindToLifecycle, zero available lenses at startup, critical thermal status (PowerManager.THERMAL_STATUS_CRITICAL), and insufficient storage (StatFs, ImageCapture.ERROR_FILE_IO, VideoRecordEvent.Finalize.ERROR_INSUFFICIENT_STORAGE).
• Define CameraErrorUiState in :ui:uistate:capture and CameraErrorUiStateAdapter + Photo Picker error string resources in :ui:uistateadapter:capture.
• Create stateless CameraErrorDialog in :ui:components:capture and wire it into PreviewLayout (CaptureLayout.kt) and PreviewScreen.kt.

Test Plan

• ./gradlew spotlessCheck --init-script gradle/init.gradle.kts
• ./gradlew :ui:uistateadapter:capture:testStableDebugUnitTest
• ./gradlew :app:assembleStableDebug

[gemini-code-assist]

Code Review

This pull request introduces a comprehensive camera error handling system, defining a domain-level CameraError sealed interface to represent various CameraX and environmental errors (such as thermal overheat and insufficient storage), mapping them to UI states, and displaying them via a new CameraErrorDialog. The feedback highlights several areas for improvement: addressing a potential UninitializedPropertyAccessException if cameraProvider initialization fails, correcting test tag names to adhere to the repository's style guide (Rule 10), adding mandatory KDoc documentation to the internal toCameraError function (Rule 11), ensuring thread safety by performing the thermal status check inside the atomic update block, and improving the storage check accuracy by verifying the actual destination directory rather than relying solely on Environment.getDataDirectory().