Add propagation of maven.repo.local on windows machine

[jedla97]

Summary

In case of linux we propagating all build arguments which also contains maven.repo.local.
This is not case on windows where we getting only specific set of them (starts with quarkus).
When #1359 was introducedThe build start separatly using maven. But when provided path to local maven repo was set as cmd argument and the artifact is not public, causing the windows failing the build of app with that forced artifact.

Tested it localy on win and it's working.

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Release (follows conventions described in the RELEASE.md)
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[michalvavrik]

Yeah, I think this patching is necessary as implementing perfect argument propagation strategy would take too much effort. Thanks for the fix.