gdb(4) fix x86 signal reporting

The existing values correspond to x86 exception vector numbers, but the
trap numbers used in the kernel do not match these 1-to-1. Prefer the
definitions from x86/trap.h, as they are what actually get passed to
kdb_trap(). This is of little consequence, as gdb_cpu_signal() only
reports the trap reason (signal number) to the gdb client.

This is limited to the subset of trap values for which kdb_trap() is
reachable.

Sponsored by: NetApp, Inc.
Sponsored by: Klara, Inc.

(cherry picked from commit 962c06c5a32deb9357851d5aca060defc79e6e90)