[ET Device Support] Annotate device attributes of CUDA backend IO tensors cuda device

[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 #18328

Update cuda backend partitioner to annotate its IO tensors as cuda device

Differential Revision: D96010436

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• [CI[B200] Smoke test encounters CUDA Unknown error for dgxb200-03 and dgxb200-04

❌ 2 New Failures, 3 Unrelated Failures

As of commit f5f20d9 with merge base 81bc830 ():

NEW FAILURES - The following jobs have failed:

• pull / unittest / macos / macos-job (gh)
  export/tests/test_target_recipes.py::TestTargetRecipes::test_mv3_model
• Test CUDA Builds / unittest-cuda / linux-job (gh)
  backends/cuda/tests/test_cuda_export.py::TestCudaExport::test_device_info_propagated_to_cuda_delegate_outputs

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

• pull / test-mcu-cortex-m-backend / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• pull / unittest-editable / windows / windows-job (gh) (matched win rule in flaky-rules.json)
  ##[error]The operation was canceled.

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