New VSCode command JDK Configuration clashes with jdkhome 'machine' scope

### Apache NetBeans version

Apache NetBeans 22 release candidate

### What happened

Using new JDK Configuration command to set all Java environments and extensions to same JDK.
In the step 3/3 select Workspace
Click OK and following warning is shown by VSCode for VSNetBeans:
It is caused by fact that in [package.json](https://github.com/apache/netbeans/blob/f328c4be53dc1d1210eeff62c098360e5574bf61/java/java.lsp.server/vscode/package.json#L114) `netbeans.jdkhome` has `scope=machine`
This kind of break the purpose of JDK Configuration command for VSNetBeans if user wants to set that to Workspace level but VSNetBeans JDK runtime can be set only at machine/user level.
This needs to be discussed how to change that.
Allow to set JDK per workspace can allow to run each instance of VSNetBeans on own JDK version? Can help projects using various JDKs open in VSNetBeans. Implications:

1. Does it affect setting `Netbeans: Userdir: Local | global`?
2. How it affects VSNetBeans when running using Remote SSH on different host with different JDK?
3. Probably more to consider...

### Language / Project Type / NetBeans Component

_No response_

### How to reproduce

Steps above

### Did this work correctly in an earlier version?

No / Don't know

### Operating System

macOS and others

### JDK

JDK indepdendent

### Apache NetBeans packaging

Apache VSNetBeans for VSCode

### Anything else

_No response_

### Are you willing to submit a pull request?

No