Kubernetes version can be editable when quitting RD with deployment profiles

[IsaSih]

Actual Behavior

Given a locked deployment profile, the kubernetes version can be editable via rdctl start even if this field is locked in the profile

Steps to Reproduce

1. Create a SYSTEM deployment profile (file under field Additional Information)
2. Start Rancher Desktop
3. Quit the application via tray menu/ run rdctl shutdown
4. Try to change the value of the locked field via rdctl start
5. Verify if the new settings is applied

Result

Rancher Desktop starts with no errors and the locked kubernetes version is actually editable via rdctl start.

"kubernetes": {
    "version": "1.23.16",
    "port": 6443,
    "enabled": true,
    "options": {
      "traefik": true,
      "flannel": true
    }

iguimaraes@isasih ~ % rdctl shutdown 
Shutting down.
iguimaraes@isasih ~ % rdctl start --kubernetes.version 1.27.2                                      
INFO[0000] About to launch /usr/bin/open -a /Applications/Rancher Desktop.app --args --kubernetes.version 1.27.2 ... 

Expected Behavior

Rancher Desktop should throw an error dialog and prevent the application to start with a value other than the specified in the locked profile.

Additional Information

profile.txt

Rancher Desktop Version

1.9.0-19-g6ccc9ccb

Rancher Desktop K8s Version

1.23.16

Which container engine are you using?

moby (docker cli)

What operating system are you using?

macOS

Operating System / Build Version

macOS Monterey

What CPU architecture are you using?

arm64 (Apple Silicon)

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

No response