Improve Quick Start tutorial for CPU-only Windows setup - draft

[smishra8]

This PR updates the docs/source/quick_start.rst file to improve reproducibility and accessibility for contributors working on CPU‑only Windows environments who are just starting and would like to see a very basic example which is runnable on CPU-builds.

Changes include:

• Clarifying installation steps for Windows users without GPU support.
• Adding explicit notes on compatibility and expected behavior.
• Providing beginner‑friendly code examples that compile and run on CPU‑only setups.

This is an incomplete draft. I am opening it early to gather feedback from maintainers and contributors before finalizing. I plan to add more descriptions and definitions for newcomers and more examples. I can also provide a Python script (similar to quick_start.py) adapted for CPU‑only builds.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

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

[meta-cla]

Hi @smishra8!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!