Decouple ui:controller:impl and ui:uistateadapter:capture from ui:components:capture

[davidjiagoogle]

Breaks the transitive dependency chain to exclude heavy development/tooling dependencies when JCA is embedded as an external library.

[gemini-code-assist]

Code Review

This pull request refactors the project by moving capture-related test tags and the DisabledReason enum from the ui:components:capture module to the ui:uistate module, while also adding corresponding localized string resources. Review feedback identifies a missing R class import in CaptureControllerImpl.kt required for string resource access and a bug where HDR_VIDEO_UNSUPPORTED_ON_LENS_TAG was assigned a duplicate string value.

[temcguir]

Decoupling ui:controller:impl and ui:uistateadapter:capture from ui:components:capture is the right goal for allowing JCA to be embedded externally.

However, moving test tags and UI string resources into ui:uistate highlights a deeper architectural issue: we are passing test tags through our state layer. Test tags in Compose are meant to identify structural UI nodes (e.g., a "Snackbar" component), not the data passing through them.

The cleanest architecture is to remove the testTag property from both SnackbarData and DisableRationale.

1. Our UI tests can find the UI element using a single static tag (like SNACKBAR_NODE_TAG defined in ui:components) and then inspect its text or semantics to verify the specific message or severity.
2. ui:controller should stop constructing SnackbarData and just emit domain events.
3. ui:uistateadapter:capture should evaluate constraints and provide the string resources for the rationales.

This severs the dependencies on test tags across the board and makes the state layer generic. I have left a few inline comments showing how we can distribute these changes.