Arm backend: Remove workaround to build TOSA serializer

[tom-arm]

• Bump version from v2025.11.0 to v2025.11.2 which includes fix

Change-Id: I3ab942211842470529fcc630fe81c1858fee1bfa

cc @digantdesai @SS-JIA @freddan80 @per @zingo @oscarandersson8218 @mansnils @Sebastian-Larsson @robell

[pytorch-bot]

🔗 Helpful Links

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

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

As of commit 1b8129e with merge base aa2aeea ():

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 323914dda4bade29ecfb623f37e299174b259a6a3b6bf05170678acc4916ae68 /exec failed with exit code 1
• pull / test-samsung-quantmodels-linux / linux-job (gh)
  RuntimeError: Command docker exec -t ce716c9eab62bd1d24bbc5a2b3e63544235eb721e25a823dcdbd481406a680c4 /exec failed with exit code 1

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 / 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'
• trunk / unittest-release / 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.

[tom-arm]

Added release notes label due to the tosa-tools version bump

[zingo]

Hi @SS-JIA is this a PR you consider you want to tests, The v2025.11.2 version is a minmal bugfixes to current v2025.11.0 mostly locking down pybinding dependancy, it was to free and picked up Pybindings 3 whan it was released a few weeks ago. e.g. this should be compatibla with the current v2025.11.0

[SS-JIA]

LGTM, this change won't impact open source tests to my knowledge. But we may have to update tosa tools again internally? Perhaps not since the update seems somewhat incremental

[tom-arm]

Failing jobs seem unrelated