Use EValue::tryTo*

[lucylq]

Use tryTo in:

• parseTensorList (tensor_parser_exec_aten.cpp) — called .toTensor()
  on each element index of a TensorList.
• parseListOptionalType (tensor_parser.h) — called .toOptional()
  on each element index of an OptionalTensorList.
• FreeCall instruction handler (method.cpp) — called .toTensor()
  on the value index being freed.

Unit tests cover parseTensorList and parseListOptionalType receiving
a non-matching EValue and expect Error::InvalidType.

Authored-with: Claude

[lucylq]

Stack from ghstack (oldest at bottom):

• Codegen: emit EValue::tryTo<T>() in boxed kernel wrappers #19041
• -> Use EValue::tryTo*  #19040

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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:

• Rolling out OSDC (ARC) runners on pull & trunk workflows in PyTorch main

❌ 2 Cancelled Jobs, 2 Unrelated Failures

As of commit d32d696 with merge base c3f3d12 ():

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• pull / unittest / macos / macos-job (gh)
  ##[error]The operation was canceled.
• pull / unittest-buck / macos / macos-job (gh)
  ##[error]The operation was canceled.

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.