tutorial for devtool debugibility

[Gasoonjia]

Summary: This diff introduces a tutorial for executorch devtool debugibility

Reviewed By: GregoryComer

Differential Revision: D90809255

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 6 New Failures, 1 Unrelated Failure

As of commit 9fb866b with merge base 176c162 ():

NEW FAILURES - The following jobs have failed:

• Lint / lintrunner-mypy / linux-job (gh)
  >>> Lint for docs/source/tutorials_source/devtools-debugging-tutorial.py:
• pull / unittest / macos / macos-job (gh)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_mv3_model
• Test CUDA Builds / check-all-cuda-builds (gh)
  Process completed with exit code 1.
• Test CUDA Builds / test-executorch-cuda-build-12.6 / linux-job (gh)
  RuntimeError: Command docker exec -t 8c9ab75ccfd27baa7bf1368d3b51cafe76e704180c25b1fc7f6ed8f8835ac399 /exec failed with exit code 1
• Test CUDA Builds / test-models-cuda (linear) / linux-job (gh)
  RuntimeError: Command docker exec -t 5fc893200a03433f7d346da1771b55b35e0fd4ac006cc080012b466484c59af4 /exec failed with exit code 1
• Test Metal Backend / test-executorch-metal-build / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?

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

• pull / test-coreml-bc-macos (macos-m2-stable) / macos-job (gh) (matched macos rule in flaky-rules.json)
  File doesn't exist

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

[meta-codesync]

@Gasoonjia has exported this pull request. If you are a Meta employee, you can view the originating Diff in D90809255.

[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.

[psiddh]

Looks like this lint failure needs to be addressed