Add get_delegated_payload utility function (#11651)

[ahmet-f-gumustas]

Summary

Add get_delegated_payload() utility function to extract delegate payloads from a graph module. The function returns a dictionary mapping delegate names to tuples of (backend_id, compile_specs, processed_bytes).

Fixes #11651

Test plan

Added 3 unit tests:

python -m unittest exir.backend.test.test_utils.TestUtils.test_get_delegated_payload_with_delegates -v
python -m unittest exir.backend.test.test_utils.TestUtils.test_get_delegated_payload_without_delegates -v
python -m unittest exir.backend.test.test_utils.TestUtils.test_get_delegated_payload_keys_match_delegates -v

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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 Unrelated Failure

As of commit b9b8384 with merge base c2ec0e8 ():

NEW FAILURES - The following jobs have failed:

• pull / test-phi-3-mini-runner-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 6599641cbaeb944a27589cdd92bf62ba821024ba75c5eb94087948243a448799 /exec failed with exit code 1
• pull / unittest-buck / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 7795047cb0c660e80a3ed24e0fc25ea52870e8fe85e6fa1eeb872522da9d5591 /exec failed with exit code 3

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

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

• pull / unittest-buck / macos / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 3

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

[meta-cla]

Hi @ahmet-f-gumustas!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[ahmet-f-gumustas]

@pytorchbot label "release notes: none"

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[ahmet-f-gumustas]

@larryliu0820 @JacobSzwejbka Friendly ping for review 🙂