orchcli init clones repos in CLI install directory instead of user's current directory

[mohit-nagaraj]

When running orchcli init, the CLI currently clones the UI and Core repositories into the directory where the
orchcli binary is installed (e.g., /usr/local/bin/), rather than the user's current working directory. This causes
several issues:

1. Permission Issues: The binary location may require elevated permissions
2. Project Organization: Users expect repos to be cloned in their current directory
3. Multiple Projects: Cannot manage multiple projects in different directories
4. Unexpected Behavior: Commands like npm install run in the wrong location

[dosubot]

The intended behavior is for orchcli init to clone the UI and Core repositories into ./ui and ./core directories relative to your current working directory—not the CLI binary's install location. The codebase confirms this: the cloning logic uses relative paths like ./ui and ./core, and all dependency installation commands run in those directories as well. There is no config or flag to change the clone destination; it's hardcoded to use your working directory source.

If you see repos cloned into /usr/local/bin/ or another system directory, it's likely because your shell's working directory was set to the binary location when you ran the command. To avoid this, make sure you run orchcli init from the directory where you want your project files to be created.

Recent documentation and merged pull requests confirm this workflow and directory structure source.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}