support etdump generation in executorch.runtime

[pytorchbot]

This PR was created by the merge bot to help merge the original PR into the main branch.
ghstack PR number: #14172 by @Gasoonjia
^ Please use this as the source of truth for the PR details, comments, and reviews
ghstack PR base: https://github.com/pytorch/executorch/tree/gh/gasoonjia/41/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/gasoonjia/41/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/main
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/gasoonjia/41/orig
@diff-train-skip-merge

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/14205

• 📄 Preview Python docs built from this PR

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

❌ 15 New Failures, 3 Pending, 4 Unrelated Failures

As of commit 2aedabb with merge base 598ba46 ():

NEW FAILURES - The following jobs have failed:

• Build Windows Wheels / pytorch/executorch / build-wheel-py3_10-cpu (gh)
  RuntimeError: Failed to install QNN SDK. Please check the logs above.
• Build Windows Wheels / pytorch/executorch / upload / upload-wheel-py3_10-cpu (gh)
  Unable to download artifact(s): Artifact not found for name: pytorch_executorch__3.10_cpu_x64
• periodic / test-models-linux (cmake, vit, portable, linux.2xlarge, 90) / linux-job (gh)
  Process completed with exit code 254.
• pull / android / build-llm-demo / linux-job (gh)
  Process completed with exit code 254.
• pull / test-llama-runner-qnn-linux (fp32, qnn_16a16w, qnn) / linux-job (gh)
  Process completed with exit code 254.
• pull / test-llama-runner-qnn-linux (fp32, qnn_8a8w, qnn) / linux-job (gh)
  Process completed with exit code 254.
• pull / test-models-linux (emformer_join, portable, linux.4xlarge.memory) / linux-job (gh)
  Process completed with exit code 254.
• pull / test-models-linux (ic3, portable, linux.2xlarge) / linux-job (gh)
  Process completed with exit code 254.
• pull / test-models-linux (resnet50, portable, linux.2xlarge) / linux-job (gh)
  Process completed with exit code 254.
• pull / test-qnn-wheel-packages-linux (3.10) / linux-job (gh)
  RuntimeError: Command docker exec -t 0e7a40e66222f3a6f43f10ac5032d4caa104015130ca2cfb949abf2b7f2be178 /exec failed with exit code 127
• pull / test-qnn-wheel-packages-linux (3.11) / linux-job (gh)
  RuntimeError: Command docker exec -t 57cc615b7f0f2457c062540c675c166dac02894df3526ebc2d5bee4db312f778 /exec failed with exit code 127
• pull / test-qnn-wheel-packages-linux (3.12) / linux-job (gh)
  RuntimeError: Command docker exec -t f30872f0647c7b283dbb541b6bf646acd25e312ae97b6bd77db91f63fd33f998 /exec failed with exit code 127
• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 053fe030db61c33cb5479d98f7dbda592db3f44bff9ba17de946fd31bd25cf1d /exec failed with exit code 23
• pull / unittest / linux / linux-job (gh)
  Process completed with exit code 254.
• pull / unittest-editable / linux / linux-job (gh)
  Process completed with exit code 254.

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / test-setup-linux-gcc / linux-job (gh) (similar failure)
  ##[error]The operation was canceled.

BROKEN TRUNK - The following jobs failed but was present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / test-binary-size-linux-gcc / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / test-moshi-linux / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / test-openvino-linux / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.

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

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[zingo]

instead of using to total size of the debugbuffer you can dig out the actual used size with something like

size_t outputdump_len = etdump_gen->get_data_sink()->get_used_bytes();

Then the file size can match the data, and also only be saved if actual data is put in the area.
I recently did this here #14143 for the arm ethos-u runner that you can look at for inspiration.