Add kernel call inputs and outputs to ETDump event tracer

[dulinriley]

Summary: We noticed that an ETDump was not logging all of the inputs and outputs in the debug buffer, and that the kernel call path didn't have the same logs that the delegate call did.

Copy the internal::event_tracer_log_evalue from the delegate path to the kernel path. This only logs when intermediate outputs are requested, and when built in the event tracer mode.

Differential Revision: D59831654

[pytorch-bot[bot]]

:link: Helpful Links

:test_tube: See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/4282

• :page_facing_up: Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

:white_check_mark: No Failures

As of commit 378d29198a659a6482debd7e584908150095f627 with merge base ef640bfa693ad4cb4c4d843c9dd6c4bf8742ad56 (): :green_heart: Looks good so far! There are no failures yet. :green_heart:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D59831654

[dulinriley]

This might not be the right fix, we're seeing some kernels log their inputs and outputs, and some other kernels not. Perhaps it's a different issue. I'll pause this for now until I can determine the real root cause.