fix: do not require a local image for k3s deploys

Kubernetes pulls the app image itself, so a k3s host is free to reap its local copy while the workload keeps running, which the `registry` plugin already does on its own. Deploys, restarts, `dokku run`, and in-cluster cron no longer assert that the image is present locally, falling back to the metadata recorded in the app's current Helm release. A `ps:restart` naming a single process type now rolls only that process type's pods rather than silently redeploying every one. Apps with an `app.json` postdeploy task still require the image locally, as that task runs on the Dokku host.

plugins/scheduler-k3s/src/triggers/triggers.go

@@ -66,7 +66,8 @@ func main() {
 		scheduler := flag.Arg(0)
 		appName := flag.Arg(1)
 		imageTag := flag.Arg(2)
-		err = scheduler_k3s.TriggerSchedulerDeploy(scheduler, appName, imageTag)
+		processType := flag.Arg(3)
+		err = scheduler_k3s.TriggerSchedulerDeploy(scheduler, appName, imageTag, processType)
 	case "scheduler-enter":
 		scheduler := flag.Arg(0)
 		appName := flag.Arg(1)