Fix state.c handling of state dump thread state

Fix state.c handling of state dump thread state

Introduce the states:

LTTV_STATE_MAYBE_USER_MODE
LTTV_STATE_MAYBE_SYSCALL
LTTV_STATE_MAYBE_TRAP

tagged by the state dump, and then checked by the fixup perform at statedump
end. The controlflow view shows "unknown" state when these states are seen, but
the fixup knows that it is safe to flag the states as "USER_MODE" and "SYSCALL"
after quiescent state has been reached.

Note that we might incorrectly assign "MAYBE_SYSCALL", and then "SYSCALL" to a
thread preempted in TRAP mode. We should find a way to add instrumentation to
the kernel so the state dump tells us how to differ between these two modes.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>