[FEAT] Enhance map creation functions with verbose debugging option

[Ebe66]

This PR…

Displays debug screen output for the two Osmosis processes under Windows when the "Output debugger logger messages" option is selected.

Considerations and implementations

Why? In the current version when an error occurs on Windows in Osmosis (batch file) the program just hangs with no feedback what so ever to the user who can only wait endlessly and doesn't get any clue to the underlying issue. Which most of the time is a Java out of heap space error.
Fixes issue: #285

How to test

1. Run program without "Output debugger logger messages" activated and observe that there is no additional screen output. Or in case of an error during Osmosis the program hanging.
2. Run program with "Output debugger logger messages" activated and observe extra/normal screen output from Osmosis and in case of an error the opportunity to see what the error is.

Pull Request Checklist

• Reviewed the Contributing Guidelines
  • Especially the Pull-Requests section
• Commits (and commit-messages) are understandable
• Tested with macOS / Linux
• Tested with Windows