fix(cli): force handling for VM lifecycle operations initiated via CLI/VMOP

[danilrwx]

Description

Fix force handling for VM lifecycle operations initiated via CLI/VMOP:

1. CLI stop now correctly propagates --force to VirtualMachineOperation.spec.force.
2. VMOP restart now honors spec.force in the powerstate controller and performs force restart path when requested.

Previously:

• d8 v stop --force had no effect because CLI hardcoded force=false for Stop VMOP.
• VirtualMachineOperation with type=Restart and spec.force=true was processed via graceful restart annotation path, effectively ignoring force behavior.

Why do we need it, and what problem does it solve?

Users expect force lifecycle actions to be applied consistently:

• stop --force should trigger force stop semantics.
• restart --force should trigger immediate restart semantics (force path), not graceful shutdown waiting behavior.

These fixes align implementation with API contract and documented spec.force semantics.

What is the expected result?

1. Run d8 v stop <vm> --force.
2. Created VirtualMachineOperation has spec.force=true and force-stop behavior is applied.
3. Create VirtualMachineOperation with type=Restart and spec.force=true.
4. Controller uses force restart path (powerstate.RestartVM(..., true)) instead of annotation-only graceful path.

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: vmop
type: fix
summary: "Force handling fixed for VM lifecycle operations: CLI stop now passes --force, and VMOP restart now honors spec.force in controller logic."