[2.11] fix(workload): clear nodeName when resetting node scheduling

[smallteeths]

Summary

Fixes #

Occurred changes and/or fixed issues

The component emits update:value, not input, so @update:value works and @input doesn’t.

2.14 issue - #16092

To Reproduce

1. Log in to Rancher v2.11.6.
2. Navigate to a cluster and open Workloads.
3. Create or edit a Deployment/Workload.
4. In the Node Scheduling section, select “Run pods on any available node” and save the workload.
5. Edit the same workload again and change Node Scheduling to “Run pods on specific nodes”, select a node, and save.
6. Edit the workload one more time and try to change Node Scheduling back to “Run pods on any available node” via the UI.

Screenshot/Video

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility
• The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base

[richard-cox]

Our general process is to resolve in master first and then backport to previous versions only when specifically needed. Are you sure it's needed here?

I've set #16092 to track 2.14.0. If backports are needed we can make those issues and then associate this PR with the one for 2.11.10

[smallteeths]

Our general process is to resolve in master first and then backport to previous versions only when specifically needed. Are you sure it's needed here?

I've set #16092 to track 2.14.0. If backports are needed we can make those issues and then associate this PR with the one for 2.11.10

Okay, I’ll submit a PR to the master branch.