feat(crates/vfox): add download_path to BackendInstall context

[malept]

Allow backend plugins to use the standard configured location to download artifacts.

[gemini-code-assist]

Summary of Changes

Hello @malept, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the vfox system by providing backend plugins with a dedicated and configurable download_path within the BackendInstallContext. This change allows plugins to consistently store downloaded artifacts in a standard location, improving organization and adherence to system configurations during the installation of tools.

Highlights

• Feature: download_path in BackendInstallContext: Introduced a new download_path field to the BackendInstallContext struct, providing backend plugins with a standardized location for downloading artifacts.
• Lua Plugin Accessibility: The download_path is now exposed to Lua-based backend plugins through the IntoLua implementation for BackendInstallContext, allowing them to utilize this path.
• Core and Backend Integration: Updated the vfox core and its backend implementation to correctly pass the new download_path during the backend_install process.
• Documentation Update: The backend-plugin-development.md documentation has been updated to reflect the addition of ctx.download_path in the BackendInstall Context, including its description and an example.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly adds the download_path to the BackendInstall context, allowing vfox backend plugins to access the standard download location. The changes are well-implemented across the struct definition, Lua conversion, function calls, and documentation. I've identified a minor inconsistency in the documentation example for install_path which should be corrected for clarity.