GotoTargetsArguments should have thread id

Currently GotoTargetsArguments provides only source, line, and column. This is not enough to identify if a given line is valid for the user to move there. It should have threadId as an argument. This will allow the debugger to validate.

# test.py
def foo():
    print('A')  # suppose thread 2 is stopped here

def bar():
    print('B')  # suppose thread 1 is stopped here
    print('C')

It is valid for thread 1 to move within the same block to print('C'). It is not valid for thread 2 to move to print('C'). There is no way to tell which thread the user wants to move from the arguments of gotoTargets request. The goto request will fail for thread 2, but this can be avoided.

For the screenshot below, I forced a blank targets response. This allows IDE to show changes to cursor indicating the move invalid

Start by locating the GotoTargetsArguments definition and the gotoTargets request in the debug adapter protocol. Trace how the request is validated and handled, then confirm that the protocol can identify the originating thread and reject invalid move targets without relying on a later goto failure.