signals-win: include the accessed address in exception reports (#62273)
Windows crash reports printed only the faulting instruction pointer, not
the address the instruction tried to access, so an access violation
report could not distinguish e.g. a NULL-field dereference from a wild
pointer or an unrecognized safepoint fault. In the julia-ci build 30
ccall-test crash, the faulting instruction was `mov 0x10(%r12),%rax` and
knowing the accessed address (~0x10, implying ptls == NULL) required
downloading the build artifact and disassembling it by hand:
https://buildkite.com/julialang/julia-ci/builds/30
Print the access kind (reading/writing/executing) and the accessed
address for EXCEPTION_ACCESS_VIOLATION and EXCEPTION_IN_PAGE_ERROR,
matching the information Unix signal reports get from si_addr.
This change was written with the assistance of generative AI (Claude).
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>