[quant][ao_migration] nn.intrinsic.qat migration to ao

[z-a-f]

Stack from ghstack (oldest at bottom):

• [quant][ao_migration] nn.intrinsic.quantized migration to ao #86172
• -> [quant][ao_migration] nn.intrinsic.qat migration to ao #86171

All quantization-related modules are being migrated to torch.ao. This migrates the nn.intrinsic.qat. Please, see the tracker for the timeline.

python test/test_quantization.py TestAOMigrationNNIntrinsic

Differential Revision: D39419993

NOTE FOR REVIEWERS: This PR has internal Meta-specific changes or comments, please review them on Phabricator!

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit our office hours

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

❌ 1 Failures

As of commit d165fb7:

The following jobs have failed:

• pr-sanity-checks

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

[jerryzh168]

I feel ideally maybe we should change the docs in one PR to avoid inconsistent docs, but looks like we already have a partially up to date doc

[z-a-f]

The docs will have to be readdressed a lot -- there are a lot of inconsistencies in the documentation. This change is here because it is needed to pass the tests though

[z-a-f]

@pytorchbot merge -f "The PR Sanity Lint error is due to large code migration. Splitting it would cause a lot of dependency issues."

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[github-actions]

Hey @z-a-f.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.