CamelHotReplacementSetup - Failed to copy resources on windows

### Bug description

Hi there !
I am the mantainer of Quarkus JNoSQL, I just want to report that on building our arangodb deployments modules (the ones requiring camel-quarkus-arangodb-deployment) we see this non-blocking error during tests :

```
2023-07-05 11:37:39,408 ERROR [io.qua.dep.dev.RuntimeUpdatesProcessor] (Timer-0) Failed to copy resources [Error Occurred After Shutdown]: java.nio.file.NoSuchFileException: C:\Users\A8ADD~1.MOS\AppData\Local\Temp\quarkus-dev-mode-test3502283492447699497\target\classes
at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:85)
at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103)
at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108)
at java.base/sun.nio.fs.WindowsFileSystemProvider.implDelete(WindowsFileSystemProvider.java:275)
at java.base/sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:105)
at java.base/java.nio.file.Files.delete(Files.java:1152)
at io.quarkus.deployment.dev.RuntimeUpdatesProcessor.checkForFileChange(RuntimeUpdatesProcessor.java:939)
at io.quarkus.deployment.dev.RuntimeUpdatesProcessor.doScan(RuntimeUpdatesProcessor.java:463)
at io.quarkus.deployment.dev.RuntimeUpdatesProcessor.doScan(RuntimeUpdatesProcessor.java:441)
at org.apache.camel.quarkus.core.devmode.CamelHotReplacementSetup$1.run(CamelHotReplacementSetup.java:36)
at java.base/java.util.TimerThread.mainLoop(Timer.java:566)
at java.base/java.util.TimerThread.run(Timer.java:516)
```

As already clarified this only happens when depending on :

```

org.apache.camel.quarkus
camel-quarkus-arangodb-deployment

```

It may be a problem related on building on windows only but maybe it's worth investigating.

Thank you !
Happy coding

Reproduce the Windows test failure with the camel-quarkus-arangodb-deployment dependency, then inspect CamelHotReplacementSetup.java:36 and RuntimeUpdatesProcessor.java:463, 939 from the stack trace. Determine why the target/classes path is missing after shutdown; done means the non-blocking resource-copy error no longer appears during the affected tests.

Written by the indexing model from the issue text.