fix: resolve pyperclip installation issue with setuptools compatibility

[Ashok-0167]

• Pin setuptools to <66.0 and pyperclip to 1.8.2 in requirements
• Add installation scripts for Linux/Mac and Windows
• Create installation fix documentation
• Update README with troubleshooting section

---

Important

Fixes pyperclip installation issue by pinning setuptools and pyperclip versions, adding installation scripts, and updating documentation.

• Dependencies:
  • Pin setuptools to <66.0 and pyperclip to 1.8.2 in requirements.
• Scripts:
  • Add install_fixed.ps1 for Windows and install_fixed.sh for Linux/Mac to handle installation issues.
• Documentation:
  • Add troubleshooting section in README.md for installation error canonicalize_version() got an unexpected keyword argument 'strip_trailing_zero'.

^{This description was created by for 8852a7b. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Caution

Changes requested ❌

Reviewed everything up to 8852a7b in 1 minute and 48 seconds. Click for details.

• Reviewed 83 lines of code in 3 files
• Skipped 1 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. README.md:144

• Draft comment:
  Ensure version specifiers match: README uses 'pyperclip==1.8.2' and 'setuptools<66.0' but scripts use range pinning. Align them for consistency.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% The comment suggests changing version specifiers but provides no evidence of inconsistency with other files. This is a troubleshooting section specifically addressing a known error with specific versions. Changing to a range could potentially introduce new issues. Without seeing the "scripts" mentioned, we can't verify if there's really an inconsistency. I could be wrong if there are scripts elsewhere in the codebase that do use different version specifiers. The range version might actually be more flexible and work just as well. Even if there are scripts elsewhere, this is a troubleshooting section specifically addressing a known error with specific versions that work. Changing to a range here could make the troubleshooting steps less reliable. Delete the comment. The suggested change lacks evidence and could make the troubleshooting steps less reliable by introducing version ranges where specific versions are known to work.

2. scripts/install_fixed.sh:22

• Draft comment:
  Add a newline at the end of the file to follow POSIX best practices.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

3. scripts/install_fixed.ps1:20

• Draft comment:
  Add a newline at the end of the file for consistency with standard practices.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_LpUG9yN3o3lCBVyh

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Use 'python -m pip' instead of bare 'pip' to ensure the correct Python interpreter is used.

Suggested change

	pip install --upgrade pip
	python -m pip install --upgrade pip

[ellipsis-dev]

It appears there might be a typo in the command at line 20: 'gtpe projects/example'. Did you mean 'gpt projects/example' or 'gpt-engineer projects/example'? Please verify the intended command.

Suggested change

	Write-Host "You can now run: gpte projects/example"
	Write-Host "You can now run: gpt-engineer projects/example"