Interrogate workflow runs, their logs, and assets / Allow user to choose to do so after basic installation + OAuth

[tyeth]

Seems my original issue was closed after Releases could be interrogated, but I needed the action run info as mentioned in the original issue, along with general other related functionality.
#150

Repeated summary here for simplicity:

I want to access the information for CI runs, to fix errors, and to fetch assets to test etc. I can use the API, but it would be helpful if the MCP server supported the requests.
Also I'd like to interrogate Releases and release assets (as well as workflow runs, the script and branch used, their logs, and assets), the description and tag and assets.

+Later clarification:

I have a matrix of many embedded build targets, the scripts and arguments are split across 3 repos.
https://github.com/adafruit/Adafruit_Wippersnapper_Arduino/actions
which uses https://github.com/adafruit/ci-arduino/tree/ci-wippersnapper and then that has a build python script and an all_platforms defintion file, which effectively relies on https://github.com/adafruit/Wippersnapper_Boards and https://github.com/adafruit/arduino-esp32/blob/wipper-3.1.3-idf-5.3/ (branch depending on all_platforms)

Upon a failure I want to be able to enquire if there was a typo etc in the new board target and if file X/Y/Z in repo A/B/C has what's expected or not, or whether there was a real issue in the code when building for that target.
The logs are huuuuge with an excess of warnings, but it's not too hard to goto them and the search for "error".
Effectively I also just wish to know why the failure occurred, but not some garbage summary based on conjecture, so that usually involves iterrogating build logs.
Sometimes there is no failure, but the firmware boot loops on certain targets so I'd potentially want to compare build logs and library versions used (raw / expanded build log), in addition assets would be obtained to run on a device or simulator. The CI jobs would most likely be being compared to a release build (and assets).

[tyeth]

It seems there is mention of such available tools in this other enhancement request issue, but I don't see such mentioned tools related to workflow in the current release on VScode (not insiders).

#924

[tyeth]

I think I might need to enable all toolsets or something, wish this was offered as a UI option as the expandable set of enablable tools for the mcp server in the vscode agent tools interface only shows already available tools. Maybe on first install the user could be presented with a welcome page or instruction to configure more toolsets to enable access to Github Action workflows + logs, etc (mention most popular disabled-by-default use-cases).

[tyeth]

Okay, installing the "all" toolset, did not include the Github Actions tools too.
Installing the gh-actions set did finally provide workflow tools 🥳

I'm changing this ticket to "Allow choosing toolsets after first installation in vscode, ideally during any session add any GH MCP toolsets to the GH MCP extension"

[tyeth]

I'll not abuse this ticket 😁 and close it instead