[ao] fixing public v private for quantize_jit.py

[HDCharles]

Stack from ghstack (oldest at bottom):

• [ao] fixing public v private for fx.backend_config_utils.py #86037
• [ao] fixing public v private for fx.quantization_types #86036
• [ao] fixing public v private for quantization_patterns.py #86034
• [ao] fixing public v private for fx.pattern_utils.py #86033
• [ao] fixing public v private for fx.graph_module.py #86032
• [ao] fixing public v private for quantization_types #86031
• [ao] fixing public v private for backend_config.native.py #86030
• [ao] fixing public v private for fuser_method_mappings.py #86029
• [ao] fixing public v private for fuse_modules.py #86028
• [ao] fixing public v private for torch/ao/quantization #86027
• [ao] fixing public v private for qconfig.py #86026
• [ao] fixing public v private for quantization_mappings.py #86025
• -> [ao] fixing public v private for quantize_jit.py #86024
• [ao] fixing public v private for quantize.py #86023
• [ao] correctly set public v private for fake_quantize.py #86022

Summary: just needed to add all

Test Plan: python test/test_public_bindings.py

Reviewers:

Subscribers:

Tasks:

Tags:

[pytorch-bot]

🔗 Helpful Links

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

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

✅ No Failures, 3 Pending

As of commit 6362cb7:
💚 Looks good so far! There are no failures yet. 💚

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

[facebook-github-bot]

/easycla

As part of the transition to the PyTorch Foundation, this project now requires contributions be covered under the new CLA. See #85559 for additional details.

This comment will trigger a new check of this PR. If you are already covered, you will simply see a new "EasyCLA" check that passes. If you are not covered, a bot will leave a new comment with a link to sign.

[HDCharles]

@pytorchmergebot merge

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered without a flag. This means that your change will be merged once all checks on your PR have passed (ETA: 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!