[executorch][nvidia][tensorrt][8/n] Add TensorRTCompileSpec dataclass

[shoumikhin]

Stack from ghstack (oldest at bottom):

• [executorch][nvidia][tensorrt][25/n] Share CUDA stream across TRT delegates #17936
• [executorch][nvidia][tensorrt][24/n] Add power and unary converters with model improvements #17935
• [executorch][nvidia][tensorrt][23/n] Add benchmark infrastructure #17934
• [executorch][nvidia][tensorrt][22/n] Add correctness tests #17933
• [executorch][nvidia][tensorrt][21/n] Add comparison and slice converters #17932
• [executorch][nvidia][tensorrt][20/n] Add bmm converter #17931
• [executorch][nvidia][tensorrt][19/n] Add SDPA converter #17930
• [executorch][nvidia][tensorrt][18/n] Add layer_norm and pixel_shuffle converters #17929
• [executorch][nvidia][tensorrt][17/n] Add embedding, expand, upsample converters #17928
• [executorch][nvidia][tensorrt][16/n] Enable MobileNetV3 model support #17927
• [executorch][nvidia][tensorrt][15/n] Add linear model support with addmm and permute_copy converters #17926
• [executorch][nvidia][tensorrt][14/n] Add additional converters (mul, sub, div, mm, relu) #17925
• [executorch][nvidia][tensorrt][13/n] Add examples, C++ runner and CI workflow #17924
• [executorch][nvidia][tensorrt][12/n] Add C++ runtime infrastructure #17923
• [executorch][nvidia][tensorrt][11/n] Complete preprocess integration with serialization #17922
• [executorch][nvidia][tensorrt][10/n] Add blob serialization format with I/O metadata #17921
• [executorch][nvidia][tensorrt][9/n] Implement preprocess basic implementation #17920
• -> [executorch][nvidia][tensorrt][8/n] Add TensorRTCompileSpec dataclass #17919
• [executorch][nvidia][tensorrt][7/n] Add converter utils and add converter #17918
• [executorch][nvidia][tensorrt][6/n] Add converter registry infrastructure #17917
• [executorch][nvidia][tensorrt][5/n] Integrate partitioner #17916
• [executorch][nvidia][tensorrt][4/n] Add operator support base class #17915
• [executorch][nvidia][tensorrt][3/n] Add TensorRT partitioner stub #17914
• [executorch][nvidia][tensorrt][2/n] Add TensorRT backend stub #17913
• [executorch][nvidia][tensorrt][1/n] Add directory structure and initialization #17912

Add TensorRTCompileSpec dataclass to configure TensorRT compilation options.

Differential Revision: D93275056

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 14 New Failures, 3 Unrelated Failures

As of commit 672d101 with merge base 01d21fa ():

NEW FAILURES - The following jobs have failed:

• pull / test-coreml-bc-macos (macos-m2-stable) / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
• Test CUDA Builds / export-model-cuda-artifact (nvidia, parakeet-tdt, quantized-int4-tile-packed) / linux-job (gh)
  RuntimeError: Command docker exec -t f49c3c2158ba8fd19490a4aa8412ad72025b2c5d483c8962202cddb195c2312f /exec failed with exit code 1
• Test CUDA Builds / test-models-cuda (add_mul) / linux-job (gh)
  RuntimeError: Command docker exec -t 8c75851b17ba349b1ad8749404a0e1fae29115db81a4fb65dfdc3322e0d150f8 /exec failed with exit code 1
• Test Metal Backend / export-model-metal-artifact (mistralai, Voxtral-Mini-3B-2507, non-quantized) / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
• Test Metal Backend / export-model-metal-artifact (mistralai, Voxtral-Mini-3B-2507, quantized-int4-metal) / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
• Test Metal Backend / export-model-metal-artifact (mistralai, Voxtral-Mini-4B-Realtime-2602, quantized-int4-metal) / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
• Test Metal Backend / export-model-metal-artifact (nvidia, parakeet-tdt, non-quantized) / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
• Test Metal Backend / export-model-metal-artifact (nvidia, parakeet-tdt, quantized-int4-metal) / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
• Test Metal Backend / export-model-metal-artifact (openai, whisper-large-v3-turbo, non-quantized) / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
• Test Metal Backend / export-model-metal-artifact (openai, whisper-large-v3-turbo, quantized-int4-metal) / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
• Test Metal Backend / export-model-metal-artifact (openai, whisper-small, non-quantized) / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
• Test Metal Backend / export-model-metal-artifact (openai, whisper-small, quantized-int4-metal) / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
• Test Metal Backend / test-executorch-metal-build / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
• Test Metal Backend / test-metal-backend-modules / macos-job (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/ec2-user/runner/_work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?

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

• periodic / test-models-linux (cmake, vit, xnnpack-quantization-delegation, linux.2xlarge, 90) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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

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

• pull / unittest / macos / macos-job (gh) (trunk failure)
  AttributeError: '_OpNamespace' 'mkldnn' object has no attribute '_is_mkldnn_acl_supported'
• pull / unittest-editable / macos / macos-job (gh) (trunk failure)
  AttributeError: '_OpNamespace' 'mkldnn' object has no attribute '_is_mkldnn_acl_supported'

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.