Added a method to walk a subtree of a given PathTree

[aloubyansky]

This PR also adds a convenient method PathTree.walkIfContains(relativePath, visitor) for walking over a subtree of a given PathTree. It's also a more efficient alternative to the current approach of using FilteredPathTree.

This PR also removes never used CachedPathTree which wasn't a complete implementation.

[gsmet]

@aloubyansky I wonder if the failure is related given I think Qute is now using this infra?

[gsmet]

@aloubyansky I think we still have a problem on Windows here.

[gsmet]

There is a log file in the PR: [extensions/qute/deployment/log](https://github.com/quarkusio/quarkus/pull/40415/files#diff-40a826f6c73b87b94607d079015516f18ae0028a85b93068ff025c1125bea062). It needs to removed.

[aloubyansky]

Yeah, I still need to debug it

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit f53be2f.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 extensions/smallrye-reactive-messaging-kafka/deployment

✖ io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase.sseStream - History

• Assertion condition defined as a Lambda expression in io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase Expecting size of: [] to be greater than or equal to 2 but was 0 within 10 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: 
Assertion condition defined as a Lambda expression in io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase 
Expecting size of:
  []
to be greater than or equal to 2 but was 0 within 10 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)

📦 extensions/smallrye-reactive-messaging/deployment

✖ io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector - History

• Expecting actual: ["-6","-7","-9","-10","-11","-12","-13","-14"] to start with: ["-6", "-7", "-8", "-9"] - java.lang.AssertionError

java.lang.AssertionError: 

Expecting actual:
  ["-6","-7","-9","-10","-11","-12","-13","-14"]
to start with:
  ["-6", "-7", "-8", "-9"]

	at io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector(ConnectorChangeTest.java:41)

[aloubyansky]

@gsmet @mkouba this one's ready for review.

This may raise a question why not always perform case-sensitive path checks. We rely on pretty much Files.exists(Path.resolve(path)) everywhere else.
What we do in case of Windows here has a certain cost, since we haven't had an issue everywhere else I thought of keeping it the way it is for now but added a method to PathTreeUtils to perform this kind of check where necessary.
If run into these issues in the future in other areas, we could reconsider the default check.

[aloubyansky]

@mkouba does it look ok to you?

[mkouba]

Looks good!