Turn on device memory planing as default

[Gasoonjia]

Stack from ghstack (oldest at bottom):

• [ET Device Support] CUDA-native Qwen 3.5 MoE inference with device tensor pipeline #18788
• -> Turn on device memory planing as default #20214
• [ET Device Support] Add device tensor helper functions to TensorPtr API #19828
• [ET Device Support] make device support config method-based #19582
• [ET Device Support] Add ExecutorchBackendConfig flags for skipping H2D/D2H copies #18760
• [ET Device Support] PropagateDevicePass inserts H2D/D2H copy ops at delegate boundaries #18730
• [ET Device Support] Add device tensor helper functions to TensorPtr API #18761

This diff turn on the on-device memory planing as default, so that every delegate which enables on device memory planing will be use that./

Also update cuda backend to remove H2D/D2H copies and extra caches

Differential Revision: D107597774

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 4 New Failures, 1 Pending, 1 Unrelated Failure, 5 Unclassified Failures

As of commit b6e6e70 with merge base b47e588 ():

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-quantmodels-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 38058b9b5e6973735ffb7e7796f1865f81d974ddc44bb7282f4f354d7ec44738 /exec failed with exit code 1
• pull / test-voxtral-realtime-xnnpack-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 7f3302e4869532ac32844d9d135cabd3785c0083746b118a4efde4633402e90d /exec failed with exit code 1
• pull / unittest / windows / windows-job (gh)
  examples/models/test/test_export.py::ExportTest::test_efficient_sam_export_to_executorch
• Test CUDA Windows Export and E2E / test-model-cuda-windows-e2e (facebook, dinov2-small-imagenet1k-1-layer, non-quantized) / windows-job (gh)
  Process completed with exit code 1.

UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:

• Test CUDA Builds / unittest-cuda / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  examples/models/gemma4_31b/tests/test_cuda_pipeline.py::TestGgufCudaPipeline::test_load_converts_weights
• Test Metal Backend / test-model-metal-e2e (mistralai, Voxtral-Mini-4B-Realtime-2602, quantized-int4-metal) / macos-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1
• Test Metal Backend / test-model-metal-e2e (openai, whisper-large-v3-turbo, non-quantized) / macos-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  ##[error]The operation was canceled.
• Test Metal Backend / test-model-metal-e2e (openai, whisper-large-v3-turbo, quantized-int4-metal) / macos-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1
• Test Metal Backend / test-model-metal-e2e (openai, whisper-small, quantized-int4-metal) / macos-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1

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

• MLX / test-mlx-voxtral-realtime / test-mlx-voxtral-realtime (gh) (detected as infra flaky with no log or failing log classifier)

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.