[FR]: Add support for runtime_toolchain_type for jq/yq/...

### What is the current behavior?

_No response_

### Describe the feature

The current toolchain only provides the binary for use during the build but no binary for the build output. People already misuse the cfg=exec binary in a cfg=target output, e.g. https://github.com/bazel-contrib/rules_oci/blob/main/oci/private/push.sh.tpl. Providing another runtime_toolchain_type (similar to what rules_java does) can help improve the current situation. Alternatively, we can provide both exec and target binary in the current toolchain and ask users to use the correct binary.

Start by tracing the existing jq/yq/... toolchain implementation and comparing its exec/target behavior with rules_java's runtime_toolchain_type. Done means the build output can use an appropriate runtime binary without misusing the cfg=exec binary, or the issue's alternative of exposing both binaries is deliberately implemented.

Written by the indexing model from the issue text.