[brentleyjones]

iOS test bundles can omit an imported dynamic framework when it is reachable only through a target in frameworks, rather than through the test's deps. The built framework is embedded, but its imported dependency is missing, which can cause a Library not loaded failure when the test bundle loads.

This brings test-bundle packaging in line with ios_application, which already collects imported frameworks through both deps and frameworks (as well as extensions). Built frameworks propagate their imported dependencies without embedding them, so the enclosing app or test bundle must package those imports alongside the built frameworks.

Propagate framework-import information through the unit and UI test frameworks attributes, and collect imports from both deps and frameworks during bundling. Continue excluding imports supplied by an in-process unit-test host. UI tests must package their own imports because their host runs in a separate process.

Adds archive-content regression tests for unit and UI tests, plus a check that imports already supplied by a unit-test host remain excluded.

Testing

• Confirmed the new unit and UI import-packaging tests fail without the fix because the imported framework is absent.
• bazel test //test/starlark_tests:ios_unit_test //test/starlark_tests:ios_ui_test --test_output=errors — all 36 tests pass with the fix.
• Buildifier formatting and lint checks pass.