more adaptive new Windows version support

[derekbruening]

Today DR bails on a new Windows version. We have code to dynamically acquire syscall numbers (modulo 3rd party hooks) but it's only used in debug build. We should use it in release to at least try to make progress on a new release (still with a warning, but non-fatal).

[derekbruening]

** TODO initial attempt

I put in code that uses the most recent ver enum and a new
windows_unknown_syscalls[] array, which is copied from the most recent
known array and then updated by decoding the wrappers. We skip any hooks,
so this is best-effort.

My test (I disabled identification of win10, and we already have
-max_supported_os_version set to 100):

% bin64/drrun -debug -- ../hello64.exe 
<Unknown Windows NT-family version: major=10, minor=0>
<Starting application C:\derek\hello64.exe (3084)>
<Initial options = -no_dynamic_options -code_api -probe_api -stack_size 56K -max_elide_jmp 0 -max_elide_call 0 -no_inline_ignored_syscalls -native_exec_default_list '' -no_native_exec_managed_code -no_indcall2direct -pad_jmps_mark_no_trace >
Hello world!
<Stopping application C:\derek\hello64.exe (3084)>

[derekbruening]

Re-opening as the very next syscall update is using the new versioning scheme where the PEB fields will remain at 10.0.sp0 forever, so we need a new way to detect a new version (probably actual syscall number checks). Xref #1825.