🔧 add .python-version file and update README with Python version requirement for building docs

[azigler]

While setting up the dev environment on Python 3.13 (default M2 Python version) I noticed the wheels dependency failed due to versioning support.

I added a file for a user's local pyenv to pick up the correct version for building the docs. I also included a note in the README:

✨ PR Description

Purpose and impact:
This PR specifies the Python version and updates documentation for local server setup.

Main changes:

• Added .python-version file specifying Python 3.10
• Updated README.md to mention Python version requirement (<=3.10)
• Minor formatting and whitespace changes in README.md

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using. We’d love your feedback! 🚀}

[orca-security-us]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Infrastructure as Code	0   0   0   0	View in Orca
Passed	SAST	0   0   0   0	View in Orca
Passed	Secrets	0   0   0   0	View in Orca
Passed	Vulnerabilities	0   0   0   0	View in Orca

[gitstream-cm]

You have used local links, use www instead.

[gitstream-cm]

You have used local links, use www instead.

[gitstream-cm]

Please mark which AI tools you used for this PR by checking the appropriate boxes:

• GitHub Copilot
• Cursor
• ChatGPT
• Tabnine
• JetBrains AI Assistant
• VSCode IntelliCode
• Claude
• Gemini
• Other AI tool
• No AI tools were used

Tip: If you want to avoid this comment in the future, you can add a label of the format 🤖 ai-* when creating your PR.

Review resolved

[azigler]

@PavelLinearB FYI, I'm unable to respond to the microsurvey, it's uneditable for me.

Review dismissed

[PavelLinearB]

@PavelLinearB FYI, I'm unable to respond to the microsurvey, it's uneditable for me.

I think it's because you don't have write permissions to the repo.. We'll fix that

Review dismissed

[azigler]

@PavelLinearB The check_local_links automation is firing but it's a false positive because this is a README. Do we need to change the rule to not label *.md? Let me know how you'd like to fix.

Also, is check_local_links on the gitStream docs? I don't see an example of that there.

[PavelLinearB]

@PavelLinearB The check_local_links automation is firing but it's a false positive because this is a README. Do we need to change the rule to not label *.md? Let me know how you'd like to fix.

Also, is check_local_links on the gitStream docs? I don't see an example of that there.

@azigler, This automation we added to protect our docs from internal links pointing to localhost, so it should be applied to README files. We should fix it to remove this false positive, and we can add it to our catalog.

[azigler]

@PavelLinearB In this case, what's triggering the automation was already there (the URL for a user's locally built docs server) and I didn't add it. How do you recommend we point them to their localhost for their docs if we cannot use a local link? I can remove the URL but that feels less helpful.