Cannot disable api nodes to remove unwanted "partner" nodes, without making new manager no longer load. Which is a bigger issue now that legacy doesn't work

### Custom Node Testing

- [x] I have tried disabling custom nodes and the issue persists (see [how to disable custom nodes](https://docs.comfy.org/troubleshooting/custom-node-issues#step-1%3A-test-with-all-custom-nodes-disabled) if you need help)

### Expected Behavior

I expect to be able to easily disable partnered nodes from showing up in my node list AND have access to node manager.

### Actual Behavior

Choose one of the two

### Steps to Reproduce

add --disable-api-nodes to command line

### Debug Logs

```powershell
N/A
```

### Other

I understand the want to improve and update everything but the push towards cloud and tying into paid services seems like it is taking precedence over usability and stability.

Start by reproducing the issue with the --disable-api-nodes command-line option, then compare whether partnered nodes are removed and whether the node manager still loads. Done means users can disable partnered nodes without losing access to the node manager.

Written by the indexing model from the issue text.