Print exception log of activity task related transaction

If a binder call is not one-way, the exception will be written to the
reply parcel without logging on server side.

If the client catches the exception silently, there is no information
about what is wrong. Even if the client prints the stack trace, the
trace is truncated by Parcel#writeStackTrace that may miss the
important calling path.

Bug: 178438487
Test: build
Change-Id: Icecd4891da8b480cc8a3bf3ae2bd7df24ed4ce45