Runner bundling/code sign in bazel instead of test runner

Currently the output of uitest rule does't do the runner bundling, instead the build system expect the runner to do this

The approach requires all external runner to implement runner bundling logic, it also require duplicate codesign logic in the runner implementation, which already exists in bazel.

I think bundling implementation in rules would deviate the responsibility from the runner imp

Start by reading the uitest rule and the Bazel build and code-signing paths that currently produce its output. Determine how runner bundling is delegated today and compare that with the existing Bazel code-signing logic. Done means the rule owns the intended bundling and signing responsibilities without requiring each external runner to duplicate them.

Written by the indexing model from the issue text.