Enhancement: Include raw call data in txlog in all cases

[haltman-at]

Does part, but not all, of #5334. Specifically the calls part; ignored the returns part for the reasons discussed there.

Adds to externalreturn actions a raw field, with either raw.calldata or raw.binary (for creations). Originally I was going to make it just a single field, but I thought it was worth distinguishing? IDK.

Btw, a thing I'd forgotten: For calls and creations that can't be decoded, we actually already include the raw data! So uh now we're including it twice in such cases. Oh well?

I wish I'd remembered that though when thinking about how to handle return values / errors / events in the first place! It would have been sensible to do those that way initially... oh well. Well, we can figure out exactly how we want this to work...

Also I updated two tests to test this stuff.

[gnidan]

Makes sense! I concur about separating the two fields for calls vs. creates.

[gnidan]

(For the redundant fields, let's just leave those for now, and we'll coordinate about it later)