Doing random post build things on IOS artifacts

Let's say I have a normal `ios_static_framework` rule. The following works as expected:

> bazel build --apple_platform_type=ios --ios_multi_cpus=arm64,armv7 :my_static_framework

Now I want to do something on the produced framework zip file by means of a `sh_binary` rule:

```
sh_binary(
name="do_things_on_framework",
data = [ ":my_static_framework" ],
srcs = [ "my_script.sh" ],
)
```
Now I try:

> bazel run --apple_platform_type=ios --ios_multi_cpus=arm64,armv7 :do_things_on_framework

And it results in spectacular misbehavior: the script is executed as if it had no dependencies and runfiles manifest has no entry for "my_static_framework". In fact, bazel ignores the platform settings outright.

What is the correct approach to add post-build steps to `ios_*_framework` or `ios_application` rules? Those are very important, yet `rules_apple` appears to break the usual Bazel logic somehow.

Reproduce the issue with the shown ios_static_framework, sh_binary, my_script.sh, and the two Bazel commands. Compare the runfiles manifest and platform settings for the framework dependency, then inspect the rules involved; done means a documented post-build approach for ios_*_framework or ios_application that preserves the dependency and respects the selected iOS platforms.

Written by the indexing model from the issue text.