## Problem Customers want to run steps using the Kubernetes executor. ## Proposal Execute a CI job via the Step Runner service for gitlab-runner~661534 according to https://docs.gitlab.com/ee/architecture/blueprints/gitlab_steps/runner-integration.html#kubernetes This includes: * Finding a good place to intercept "regular" `script` execution and replace it with delegation to steps. * Creating `RunRequest` from the Job request (https://gitlab.com/gitlab-org/gitlab-runner/-/issues/37413). * Creating a connection function that will (ab)use the `kubectl exec` protocol and allow sending `gRPC` requests over it (See https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/4555 for working example for gitlab-runner~401313). * Using the step service client library to manage the entire execution lifecycle. * Step Runner service logs should be streamed to the CI job trace log. * Step Runner `StepResults` can be `/dev/null` for now. * Copying the `step-runner` binary to the target host, making sure the `steps-runner` service is running and listening on a local socket (see https://docs.gitlab.com/ee/architecture/blueprints/gitlab_steps/runner-integration.html#non-goals).