[ET-VK][ez] Introduce a graph config setting to force resize functions to execute

[SS-JIA]

Stack from ghstack (oldest at bottom):

• [ET-VK] Introduce specialized implementation for per-row reduction #15161
• [ET-VK] Contiguous buffer implementation for embedding #15160
• [ET-VK] Implementation of pow.Tensor_Scalar #15159
• -> [ET-VK][ez] Introduce a graph config setting to force resize functions to execute #15158
• [ET-VK] Introduce TextureMetadata struct #15157
• [ET-VK][ez] Allow bool tensors to be lowered to ET-VK and add uint8(bool) dtype variants for several compute shaders #15155
• [ET-VK][ez] Make pipeline executable properties be controlled by a different macro #15154
• [ET-VK][ez] Accept sample_kwargs as an argument in several test util functions #15153

Title says it all! A few months back, a mechanism was introduced where an ExecuteNode would not call an operator's resize function if none of the arguments were updated.

However, this creates a blind spot during testing where the resize function of operators are not tested since the generated operator tests do not modify input sizes.

To address this, add a way to force the resize function to be called during testing.

Differential Revision: D84716451

[pytorch-bot]

🔗 Helpful Links

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

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

• AWS was down, GHA infrastructure effected / recovering

❌ 2 New Failures, 4 Pending, 4 Unrelated Failures

As of commit 14ac9ed with merge base 7349bb5 ():

NEW FAILURES - The following jobs have failed:

• pull / android / run-emulator (gh)
  The process '/usr/bin/sh' failed with exit code 255
• pull / unittest-nxp-neutron / linux-job (gh)
  RuntimeError: Command docker exec -t aa4b35a888ded74ff0e0c301736bbfe59bd66f0254aa03d581970e2f757f717f /exec failed with exit code 1

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

• pull / test-models-linux (mobilebert, portable, linux.2xlarge) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)
• pull / unittest-arm-backend-with-no-fvp (test_pytest_models) / linux-job (gh) (matched linux rule in flaky-rules.json)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
• pull / unittest-editable / linux / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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 / linux / linux-job (gh) (trunk failure)

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.