Netbeans debugger doesn't support changing parameters in classes

### Description

I just started testing jRebel and used jRebel's plugin. Everything seems to work fine on jRebel side.

## Steps
**Step 1**. I've setup jRebel in large project ([used the Maven plugin method](https://manuals.jrebel.com/jrebel/standalone/maven.html)).

**Step 2**. Deployed project via Netbeans (CTRL+F5).

**Step 3**. I add a parameter:

E.g. I have this method:
```java
@RequestMapping(method = RequestMethod.GET)
@ResponseBody
public ExtJSResultListGrid getList(
@RequestParam(value = "query", required = false) String query,
HttpSession session
) throws RequestFailedException, IOException {
final LibrarianContext librarianContext = librarianContextProvider.getLibrarianContext();
checkContext(librarianContext, session);

var listDTO = readerService.list(librarianContext, query);
return new ExtJSResultListGrid(listDTO);
}
```
Change it to add test11 param:
```java
public ExtJSResultListGrid getList(
@RequestParam(value = "query", required = false) String query,
@RequestParam(value = "test11", required = false) String test11,
HttpSession session
) throws RequestFailedException, IOException {
LOG.warn("jRebel test11: {}", test11);
```

**Step 4a**. I get this in Tomcat log:
```
2025-09-29 17:22:21 JRebel: Reloading class 'pl.mol.molnet.ext.reader.ReaderController$UpdateManyParams'.
2025-09-29 17:22:21 JRebel: Reloading class 'pl.mol.molnet.ext.reader.ReaderController'.
2025-09-29 17:22:22 JRebel: Reconfiguring reprocessed bean 'readerController' [pl.mol.molnet.ext.reader.ReaderController]
```

**Step 4b**. But I also get this in Netbeans Debugger Console:
```
The debugger does not support Hot Fix action, details: delete method not implemented
```

**Step 5**. I refresh view and I get the new log:
```
2025-09-29 17:22:29.0050 WARN : pl.m.ext.reader.ReaderController jRebel test11: null
```

### Use case/motivation

It seems like hot fix works on the server (Tomcat) but the Netbeans debugger cannot handle it. It seems like something Netbeans can fix, right? Or is the debugger replaceable by plugins (and perhaps there is better debugger already)?

As I understand same steps should work in InteliJ.

### Related issues

_No response_

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

No

Start by reproducing the reported Java parameter change with JRebel, Tomcat, and NetBeans Debugger using the listed deployment and refresh steps. Compare the JRebel reload messages with the NetBeans debugger console error, "delete method not implemented"; done means the debugger handles the change without reporting that unsupported Hot Fix action.

Written by the indexing model from the issue text.