Orbit/Galaxy MCP: no way to save/import a generated .ga workflow into the user's Galaxy Workflows

A tester had Orbit generate a Galaxy workflow file (`*.ga`) in the local workspace, then asked where it was saved in their Galaxy account. Orbit explained it can't import a local `.ga` into the user's Galaxy Workflows list -- the MCP surface has list/get/run/invoke and `import_workflow_from_iwc`, but no "import this local .ga" tool -- so the file just stays in the local workspace.

This is a galaxy-mcp tool-surface gap; tracking here since that's where testers feel it. One of a small set of "missing Galaxy operation" reports filed together -- see siblings for Data Libraries, dataset purge, and paired-collection build.

---
Filed together as the missing-Galaxy-operation set: #226 (Data Libraries), #227 (workflow import), #228 (dataset purge), #229 (paired-collection build).