Specify the Path of the Golang Executable

[mfcollins3]

Closes #754

I enhanced GolangAppHostingExtension to define a new override of AddGolangApp that allows specifying the path of the Golang executable relative to the working directory. This is useful for scenarios where the Golang executable is in a cmd subdirectory, but the working directory needs to be the root of the project for accessing resources relative to the working directory at runtime. It is also useful when there are more than one executable in a Go module.

I updated the existing AddGolangApp method to call the new overload passing . as the executable path. This will support existing consumers without breaking their integrations.

PR Checklist

• Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
• Based off latest main branch of toolkit
• PR doesn't include merge commits (always rebase on top of our main, if needed)
• New integration
  • Docs are written
  • Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
• Tests for the changes have been added (for bug fixes / features) (if applicable)
• Contains NO breaking changes
• Every new API (including internal ones) has full XML docs
• Code follows all style conventions

Other information

[tommasodotNET]

Thank you for your contribution! I'm currently oof, I'll be back on the 26th, and I'll review this pr asap 🙂

[mfcollins3]

Thank you for your contribution! I'm currently oof, I'll be back on the 26th, and I'll review this pr asap 🙂

@tommasodotNET This PR got closed. Can you re-open it?

[tommasodotNET]

lgtm, thanks!