Make the debounce time of publish diagnostic job adaptive

[jdneo]

Now the debounce time of publish diagnostic jobs are adaptive. Ranging from [400, 2000] ms.

Signed-off-by: Sheng Chen sheche@microsoft.com

How to test the impact of this change:

1. Add lombok dependency to petclinic project.
2. Toggle on the setting java.trace.server to messages, which will let the client print all the response time in the output channel.
3. Use this attached file to replace PetControllerTests.
4. Launch the language server.

   Remember to add the lombok agent to the launch file when debugging.

5. After the projects are imported and no more output can be observed in the output channel, clear the output channel.

   The project import traces are not related with this change, so we filter them out.

6. In the last method void testProcessUpdateFormHasErrors26(), do some modification to trigger different kinds of LSP requests. When I test it locally, I typed System.out.println(); and then use Backspace to remove the typed characters one by one.
7. Wait until no more output can be observed, then we can analysis the average time cost to process each of the request. For example, copy the output to a file and scan it line by line. Regular Expression like /\[Trace.*\] Received response \'.*\' in (\d+)ms/ can help us pick the time out.

Test Result

By doing the above experiment according to the above steps with and without PR, the average time cost to process a request list below:

	Time(ms)
Without the change	633
With the change	325

My machine is a Windows 10 with i7-10700 2.9GHz CPU.

---

Looks like the change works well from the customer's feedback: redhat-developer/vscode-java#1765 (comment)