Fix Windows Spring Boot Process Application Resource Scanning in 2.0.x

[ryans58]

Summary

Fixes Windows Spring Boot process application resource scanning when using @EnableProcessApplication with an empty META-INF/processes.xml.

Beginning with Fluxnova 2.0.3, ClassPathProcessApplicationScanner can receive a Windows drive-letter path from URL.getPath() in the form:

/C:/dev/fluxnova-loan-review/target/classes/META-INF/processes.xml

Passing that value directly to Paths.get(String) causes Windows to reject the drive-letter colon with:

java.nio.file.InvalidPathException:
Illegal char <:> at index 2

Change

The scanner now normalizes this specific Windows path representation before passing it to Paths.get(...):

/C:/dev/... -> C:/dev/...

The change is intentionally narrow and preserves the existing resource-scanning and path-normalization behavior for other platforms and resource types.

A focused unit test has also been added to cover Windows drive-letter path normalization without requiring the test suite itself to run on Windows.

Validation

The fix has been validated against the full Fluxnova test suite using:

mvn clean install

The patched scanner has also been successfully tested with a Spring Boot process application on Linux.

Windows validation has been performed against the affected Fluxnova releases using a Spring Boot process application with:

• @EnableProcessApplication
• an empty META-INF/processes.xml
• automatic BPMN resource discovery

The same process application works correctly without the patch on Fluxnova 2.0.0, 2.0.1 and 2.0.2.

Fixes #286 in versions 2.0.3 and 2.0.4. A separate PR will be proposed to fix the issue in 3.0.0.