Fix dynamic data arguments

[josedonizetti]

Fix #3771

This PR fixes the parsing of types on arguments (signatures) that aren't supported by grpc event data. The idea is that users can create signature and pass whatever information as finding.Data to fit their needs, but this information must be converted properly to protobuf so the GRPC api can return it when streaming events.

I've tried a few solutions, but it always endup using reflection if tracee was the one responsible to convert the type, which is slow and cubersome, for example, we are only able to read exported fields, nested need deeper logic for convertion. So instead a better solution is to ask the user which information he wants to send on the grpc by implementing an interface, if the interface is implemented tracee calls it and use that data for the argument (kuddos to @NDStrahilevitz for the idea).

Also, we don't break the logic anymore if we can't parse an argument, we log and send the event with the missing data if needed.

Depends

#3776

[yanivagman]

LGTM