Preserve BatchNorm running state in composable quantizer

[denizkilinc]

Summary:
Quantization-aware training with the composable PatternQuantizer incorrectly observed BatchNorm affine parameters and running-state buffers as activation inputs. The inserted fake-quant nodes broke the connection between aten.batch_norm.default and the registered running_mean and running_var buffers, so training used batch statistics while evaluation consumed stale running statistics.

Keep aten.batch_norm.default arguments 1-4 directly connected to registered state by excluding them from activation observation while retaining activation and output quantization. Add Arm and Sleep/ModAI regression tests that verify the state operands remain registered and the running statistics update during QAT.

Differential Revision: D112989631

[pytorch-bot]

🔗 Helpful Links

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

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

• Unrelated MacOS MPS test jobs time out (30 min) due to stale cpp_extension lock file poisoning self-hosted runners

❌ 1 New Failure, 1 Cancelled Job, 1 Unrelated Failure

As of commit b0fcdc3 with merge base 667c91b ():

NEW FAILURE - The following job has failed:

• pull / unittest-buck / linux / linux-job (gh)
  RuntimeError: Command docker exec -t dd2584714235a3dd7a2b844dd2ea991cfd57b0d5782507c86da05154ca720ab8 /exec failed with exit code 3

CANCELLED JOB - The following job was cancelled. Please retry:

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

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-buck / macos / macos-job (gh) (trunk failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 3

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[linux-foundation-easycla]

• ❌ - login: @denizkilinc / name: Deniz Kilinc. The commit (b0fcdc3) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

[meta-codesync]

@denizkilinc has exported this pull request. If you are a Meta employee, you can view the originating Diff in D112989631.

[pytorch-bot]

Workflows were awaiting approval. CI has now been triggered for the ciflow labels on this PR.

[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.

[denizkilinc]

/easycla

[rascani]

LGTM, but you'll need to sign EasyCLA. Let me know if you need any help with that.

[denizkilinc]

@rascani thank you for the review. I signed EasyCLA, now waiting for approval. If don't get approval today, I'll let you know.