Migrate executorch/ tests from exir.capture to torch.export + to_edge

[JacobSzwejbka]

Summary:
Migrate test_pass_infra, test_debug_handle_map, test_delegate_map_builder,
test_backends_nested, and hta_partitioner_demo to use the torch.export.export()

• to_edge() flow instead of the deprecated exir.capture() API.

Key changes:

• Replace exir.capture(model, inputs, CaptureConfig()).to_edge() with
  to_edge(export(model, inputs, strict=True))
• Wrap plain functions in nn.Module for torch.export compatibility
• Use dynamic debug handle extraction instead of hardcoded values in
  test_delegate_map_builder (handle numbering changed)
• Collapse lifted/unlifted pattern variants in hta_partitioner_demo
  since torch.export always produces lifted graphs

Differential Revision: D95605454

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 1 Pending, 2 Unrelated Failures

As of commit e1aa5b3 with merge base 090af6c ():

NEW FAILURES - The following jobs have failed:

• Build Presets / windows (pybind) / build (gh)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 1
• Build Presets / windows (windows) / build (gh)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 1

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

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

• pull / unittest / windows / windows-job (gh) (trunk failure)
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  The process 'C:\Program Files\Git\cmd\git.exe' failed with exit code 1

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

[meta-codesync]

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

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