Add Frappe Repo Path

[grawish]

Description
Add a configurable option in the frappe-manager repository to specify the path to the Frappe repository. This feature would enable developers to easily manage and deploy custom Frappe builds without relying solely on the default Frappe path. The feature should allow setting this path during setup or via environment variables.

Use Case
This feature would be beneficial in scenarios where:
1. Developers use a custom fork of the Frappe framework and need to point frappe-manager to their specific repository path.
2. Multiple Frappe installations exist on the same server, each requiring a different version or custom build of Frappe.
3. Testing or development workflows require switching between different Frappe repositories seamlessly.

Expected Behavior
• A configuration option is available in frappe-manager to specify the Frappe repository path.
• frappe-manager should recognize this path and use it during setup, build, and deployment processes.
• The path can be set during installation or updated later via the configuration file or environment variables.

Current Behavior (if applicable)
Currently, frappe-manager does not provide an option to specify a custom Frappe repository path. It defaults to the standard installation process, which may not align with custom or forked Frappe setups. Users must manually manage paths, leading to additional effort and potential misconfigurations.

Possible Solution
1. Add a configuration parameter (e.g., frappe_repo_path) to frappe-manager.
2. Allow this parameter to be set during installation via prompts or passed as an environment variable.
3. Update the installation scripts and deployment workflows to respect the configured path.
4. Provide validation to ensure the specified path contains a valid Frappe repository.

Additional Context
This feature aligns with the modular and customizable nature of Frappe. It also ensures that frappe-manager can cater to a wider range of development and deployment use cases.

Related Issues/Pull Requests
• No known related issues or PRs at the moment.