uds run slim-dev fails when there is not k3d cluster present

[cmwylie19]

Environment

Device and OS: Mac
App version:

> k3d version 
k3d version v5.7.4
k3s version v1.30.4-k3s1 (default)

There is an easy workaround to get around this but just wanted to report incase others are seeing this. Happy to help reproduce as well if you all don't have macs, but when running uds run slim-dev without an existing k3d cluster, it fails early on a KFC command. The work around is to k3d create cluster and then run the uds run slim-dev

Steps to reproduce

1. k3d cluster delete --all
2. uds run slim-dev

Expected result

Starts deploying slim-dev

Actual Result

       dist/pepr-uds-core.js.LEGAL.txt                                                           0b   100.0%                                 
                                                                                                                                             
     {"level":30,"time":1731339801547,"pid":22212,"hostname":"Cases-MacBook-Pro.local","component":"config","domain":"uds.dev","caCert":"","allowAllNSExemptions":false,"authserviceRedisUri":"","isIdentityDeployed":false,"msg":"Loaded UDS Config"}
     /Users/cmwylie19/uds-core/node_modules/kubernetes-fluent-client/dist/fluent/utils.js:80                                                 
             throw new Error("No currently active cluster");                                                                                 
                   ^                                                                                                                         
                                                                                                                                             
     Error: No currently active cluster                                                                                                      
         at k8sCfg (/Users/cmwylie19/uds-core/node_modules/kubernetes-fluent-client/dist/fluent/utils.js:80:15)                              
         at reconstruct (/Users/cmwylie19/uds-core/node_modules/kubernetes-fluent-client/dist/fluent/utils.js:110:43)                        
         at k8sExec (/Users/cmwylie19/uds-core/node_modules/kubernetes-fluent-client/dist/fluent/utils.js:121:33)                            
         at Object.Get (/Users/cmwylie19/uds-core/node_modules/kubernetes-fluent-client/dist/fluent/index.js:147:36)                         
         at initAPIServerCIDR (/Users/cmwylie19/uds-core/dist/pepr-uds-core.js:1:5159)                                                       
         at Object.<anonymous> (/Users/cmwylie19/uds-core/dist/pepr-uds-core.js:1:40277)                                                     
         at Module._compile (node:internal/modules/cjs/loader:1460:14)                                                                       
         at Module._extensions..js (node:internal/modules/cjs/loader:1544:10)                                                                
         at Module.load (node:internal/modules/cjs/loader:1275:32)                                                                           
         at Module._load (node:internal/modules/cjs/loader:1091:12)                                                                          

Visual Proof (screenshots, videos, text, etc)

Severity/Priority

i would argue very low since there is a workaround and this is possibly only a bug on mac

Additional Context

Add any other context or screenshots about the technical debt here.