Resolve the TODO at cmd/nodepool/kubevirt/create.go line 295: "TODO: add a debug trace for this error".

Why

When ParseQuantity fails for an invalid --memory value, the error is silently swallowed and the code falls back to a default. Operators have no way to diagnose why their specified memory value was ignored.

Acceptance Criteria

• Log the ParseQuantity failure at debug level before falling back to the default
• Include the invalid input value and the error message in the log output
• Remove the TODO comment from the source

Technical Details

• File: cmd/nodepool/kubevirt/create.go line 295
• TODO text: "TODO: add a debug trace for this error"
• Context: ParseQuantity error handling for the --memory CLI flag