[ET Device Support] Parse device info from serialized tensor in tensor_parser

[Gasoonjia]

Stack from ghstack (oldest at bottom):

• [ET Device Support] Annotate device attributes of CUDA backend IO tensors cuda device #18080
• -> [ET Device Support] Parse device info from serialized tensor in tensor_parser #18310
• [ET Device Support] Propagate device info from TensorSpec into serialized Tensor #18079
• [executorch] Propagate device metadata from partitioner result onto TensorSpecs #18078
• [ET Device Support] TensorImpl carries device info #17534
• [ET Device Support] Schema changes: device info on Tensor and buffer-level device array #17533

Parse device info (device_type, device_index) from the serialized ExtraTensorInfo in .pte files into TensorImpl at runtime.
When a tensor's extra_tensor_info contains device annotations (e.g., CUDA), the tensor parser now reads and propagates them to the TensorImpl constructor. Tensors without extra_tensor_info default to CPU/0 for backward compatibility with older PTE files.、

Differential Revision: D97199497

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 4 Unrelated Failures

As of commit 88142f3 with merge base 569cf41 ():

NEW FAILURES - The following jobs have failed:

• pull / unittest-buck / linux / linux-job (gh)
  [ FAILED ] DeviceTest.ImplicitConstructionFromDeviceType
• pull / unittest-buck / macos / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 32

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• pull / test-llama-runner-linux-android / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• pull / test-static-llama-qnn-linux (stories_110m) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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)
  ##[error]The operation was canceled.
• pull / unittest-editable / windows / windows-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.