RFR: JDK-8256864: [windows] Improve tracing for mapping errors

[Thomas Stuefe]

To analyze JDK-8256729 further, we need more tracing:

1) We should print all mappings inside the split area if os::split_reserved_memory() fails

2) The print-mapping code on windows has some shortcomings:
- should not probe for mappings outside of what we know are valid address ranges for Windows
- should handle wrap-arounds - it should be possible to print the whole address space
- Protection information is printed wrong (MEMORY_BASIC_INFORMATION.Protect would be the correct member)
- should be printed in a more compact manner - base address should be on the same line as the first region
- maybe adorned with some basic range info, e.g. library mappings

-------------

Commit messages:
 - Initial patch

Changes: https://git.openjdk.java.net/jdk/pull/1390/files
 Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=1390&range=00
  Issue: https://bugs.openjdk.java.net/browse/JDK-8256864
  Stats: 89 lines in 4 files changed: 75 ins; 2 del; 12 mod
  Patch: https://git.openjdk.java.net/jdk/pull/1390.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/1390/head:pull/1390

PR: https://git.openjdk.java.net/jdk/pull/1390