Tekton Client plugin always runs on the Jenkins controller (Jenkins Agent Support)

Tekton Client plugin steps is using the `SimpleBuildStep` API which requires provisioning of agent and workspace, Bit all steps actually run on the Jenkins server instance, `Launcher` remote calls are not invoked. It would be great to support actually running steps on agents

Start by tracing the Tekton Client plugin steps that implement the SimpleBuildStep API and inspect how their Launcher calls are used. Verify whether the calls execute on the Jenkins controller or the provisioned agent workspace. Done means the steps perform their work through the agent and remote Launcher rather than running on the Jenkins server.

Written by the indexing model from the issue text.