fixed mixed output of adapter and regular traces

[lslusarczyk]

Fixed #2002 issue.
Regular UR tracing prints calls in two separate lines like PI does.

[pbalcer]

I'm not really a fan of this approach, I'd prefer to have indents like ltrace. But I guess it solves the immediate problem...

Also, please try to keep the first line of the commit message under 50 characters, and the rest of the message lines under ~70.

$ man git commit

...
Though not required, it’s a good idea to begin the commit message with a single short (less than 50 character)
line summarizing the change, followed by a blank line and then a more thorough description. The text up to the
first blank line in a commit message is treated as the commit title, and that title is used throughout Git.

[pbalcer]

not all the arguments can be accessed here, because some of them may be output arguments, with uninitialized content, which results in UB on access.

We either have to selectively access the parameters, adding an option to printFunctionParams to decide whether we are pre or post function execution, or, we can simply read those arguments after the execution. Which is what the original implementation did, for this exact reason.