fix: Resolves issues with namespacing if the namespace has to be different than orka-default

[jasonjanderson]

Summary

• WaitForImage was hardcoded to use DefaultOrkaNamespace instead of the configured namespace, causing image saves to fail when the VM builder namespace differs from orka-default
• Updated WaitForImage (interface, implementation, and mock) to accept a namespace parameter and pass it through to the underlying watcher
• Fixed stepCreateImage cleanup and imageSaveNFS to use config.OrkaVMBuilderNamespace instead of the hardcoded DefaultOrkaNamespace

Changes

• builder/orka/orka_client.go: Added namespace parameter to WaitForImage interface and implementation; pass namespace to waitForImage instead of DefaultOrkaNamespace
• builder/orka/step_create_image.go: Use config.OrkaVMBuilderNamespace in both image cleanup and imageSaveNFS creation/wait calls
• mocks/orka_client_mock.go: Updated mock to match the updated WaitForImage interface signature

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ispasov]

Hey,

Images are only available in the default namespace. This is the reason the namespace is hardcoded.

What is the error that you are getting when the namespace is different?