MR: Pending ## Description Currently, we use hand-generated mocks in the remote development module in the GitLab Kubernetes agent for testing purposes. These are difficult to maintain and could lead to flaky tests. we should look into alternatives that rely on code generation from interfaces, where we can explitily set what calls we expect to receive and desired behaviour. <!-- Replace with other type, e.g. bug or maintenance, if appropriate --> <!-- Replace with other subtype if appropriate --> <!-- By default, all issues start in the unprioritized status. See https://handbook.gitlab.com/handbook/engineering/development/dev/create/remote-development/#-planning-process --> <!-- For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase -->