[GR-21865] Introduce copy-on-write image heap provider on Windows.

[pejovica]

This PR adds a copy-on-write image heap provider for Windows.

A few high-level notes on implementation:

• New image heaps are provided by memory mapping views of the loaded image heap.
• In case of failure to map a new image heap, the implementation falls back to copying from memory as before.
• For memory mapping to work, the OS must have support for memory placeholders. This is checked at runtime as not all Windows versions have the necessary support.
• The use of memory placeholders is transparent to the rest of the system, i.e., it is completely encapsulated in WindowsVirtualMemoryProvider .

[joerg-wille]

This PR breaks compatibility with upx.
It is desirable to achieve minimum app size for which upx is commonly used to compress nativ Image.

Some ideas for a more proper fix:

• Compare the static parts of the in-memory image heap with the mapped file and fall back to super.commitAndCopyMemory when not matching
• Create a paging file backed (INVALID_HANDLE_VALUE) file mapping object, copy the uncompressed image heap to it and then that can be used and shared the same way as the mapped executable file

Originally posted by @kornelpal in upx/upx#559 (comment)