VSCode extension allows to 'delete' dependencies from project with various results.

### Apache NetBeans version

Apache NetBeans 17

### What happened

The following issues were found:
- Delete on direct dependency in Maven deletes the entry from the POM. But if the POM is opened in the active editor, the change is only visible after switching active editor to another file and back, or after switching from vscode to another app and back.
- Delete on *transitive dependency* has no effect at all from vscode. In NB IDE, there's `Exclude dependency` action that could be used. The `Delete` should either not be present, or map to the `Exclude dependency`.
- Delete on Gradle dependencies has no effect. NB IDE does not allow to delete the dependency (the only actions are download javadoc and sources).
-

### How to reproduce

Open a maven and a gradle project in vscode. For example some Micronaut project (see http://launch.micronaut.io for the project generator, allows to create with both build systems) In Maven project, inspect the `Dependencies` node; in Gradle project `Configurations/compileClasspath node` - they show jar dependencies that offer `Delete` context action.

- explorer the dependency (.jar) nodes
- observe context actions offered on right-click on the JAR files
-

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

No / Don't know

### Operating System

Ubuntu 22.04

### JDK

java version "11.0.5" 2019-10-15 LTS

### Apache NetBeans packaging

Apache VSNetBeans for VSCode

### Anything else

_No response_

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

No

Reproduce the issue in the VSCode dependency explorer using the Maven Dependencies node and the Gradle Configurations/compileClasspath node. Check the Delete context actions for direct and transitive JAR dependencies; done means Maven updates are reflected immediately, transitive dependencies use an appropriate exclusion action, and Gradle dependencies no longer offer an ineffective Delete action.

Written by the indexing model from the issue text.