apple_dynamic_framework_import regressions

4ec36b79fd35633581f5e1eb51c0bc7aac3f6031 regressed `apple_dynamic_framework_import` in a couple ways:
- ~Generated provisioning profiles no longer work, since they aren't listed as an input into `ImportedDynamicFrameworkProcessor`~ Fixed with #856
- ~`ImportedDynamicFrameworkProcessor` needs `execution_requirements = {"no-sandbox": "1"}` when there is a provisioning profile otherwise the sandbox blocks it~ Fixed with #862
- When using `ipa_processor` a framework that is stripped of its code signature is no longer re-signed (in particular for us, when we strip bitcode and Swift symbols from a framework)

Start by tracing the apple_dynamic_framework_import path through ipa_processor and ImportedDynamicFrameworkProcessor, focusing on the code-signature handling after framework stripping. Done means a stripped framework is re-signed again, while the provisioning-profile regressions remain covered by fixes #856 and #862.

Written by the indexing model from the issue text.