Trigger restart when deleting previously existing watched file

[Postremus]

Also fixes naming of the processor responsible for the initial watched files scan

Fixes #25331

[Postremus]

Will have to take a closer look why the maven tests failed, looks related.

[Postremus]

Setting to draft, I want to do a full CI run in my fork first. I also need to possible do a bit more cleanup before this is ready.
DevMojoIT#testThatMultipleResourceDirectoriesAreSupported now passes locally though.

I found the reason why the tests where failing.
It is related to them having multiple resource directories, and me introducing deletion of single files in target/classes when these get deleted in the resource directory.

Basicly, it went like this.
resource-dir-a: contained application.properties
resource-dir-b: no application.properties

First, resource-dir-a was checked. application.properties was found - no need to delete anything.
resource-dir-b got checked for application.properties. which was not found. Now, the file got deleted from the outputdir, even though it existed in another resource root.

[Postremus]

CI passes in my fork, this is now ready for review.

[aloubyansky]

Looks good, @Postremus, thanks! Would be good to have a test for it though. Will you have time to add one? Just in case it helps, we already have some test projects that include extensions, e.g. https://github.com/quarkusio/quarkus/tree/main/integration-tests/maven/src/test/resources-filtered/projects/project-with-extension.

[Postremus]

@aloubyansky I added one in DevMojoIT.

[aloubyansky]

Excellent. Thanks @Postremus !