Feature/dove graph

[jonnyz32]

Introduce a new CytoscapeGraph class to manage graph elements and display them in a webview. Enable node selection to show detailed information.

Tasks:

• Merge in missing commits from main
• Fix that 'Run and explain' doesn't open the view, but 'Explain without running does'
• Improve formatting of nodes in webview
• stretch: Determine if coloring each node can be based on the old logic
  https://github.com/codefori/vscode-db2i/blob/main/src/views/results/explain/doveTreeDecorationProvider.ts#L38
• stretch: See about embedding icons onto nodes
  Here are the attached icons for each different node type: https://github.com/codefori/vscode-db2i/blob/main/src/views/results/explain/doveResultsView.ts#L13
  Perhaps you need this to embed the icons into the webview? https://github.com/microsoft/vscode-codicons
• Attach description to each node if applicable
  Old logic here: https://github.com/codefori/vscode-db2i/blob/main/src/views/results/explain/doveResultsView.ts#L126
• Stop using remote URL to pull in cytoscape and embed into the build
• Update icon.ts to include all possible labels

Screen.Recording.2025-07-17.at.1.51.15.PM.mov

[worksofliam]

The UX is looking really good, but there are some things in the code we'll need to cleanup before merge.

context

We don't typically want to store the extension context as a global, and we usually want to pass it all the way down where possible. The route I would take is to start by deleing the contextProvider.ts file and seeing how you can mangle it down there.

build files (media)

We add a new dependency in this PR - cytoscape - but, we should not be checking in this file into our git repository. Instead, at build time, we should be pulling it from the installed node_modules.

The remaining files make sense, since it's written outside of a package and is part of the extension.

[worksofliam]

So typically in extension, we don't store the context globally. We always pass the instance down in the activate function. For example, you might pass it down to resultsProvider.initialise and do the work there.

[worksofliam]

again, shouldn't be using this context provider. Instead, the context could be stored as a private member property passed in from the constructor.