feat: add createGPUDroplet, getGPUDroplet, updateGPUDroplet and deleteGPUDroplet components

[felixgateru]

Implements: #3484

What changed:

Added four new DigitalOcean GPU droplet management components: Create GPU Droplet, Get GPU Droplet, Update GPU Droplet, and Delete GPU Droplet.

Why:

Enable users to provision and manage GPU-powered DigitalOcean droplets.

How:

Backend:

• Created four new component files in pkg/integrations/digitalocean/
• Extended client.go with GPU-specific methods
• Updated list_resources.go to handle new GPU resource types
• Added tests

Frontend:

• Created UI mappers in web_src/src/pages/workflowv2/mappers/digitalocean/
• Registered all mappers and event states in index.ts

Demo

https://youtu.be/X-xxFkwiV1w

[superplanehq-integration]

👋 Commands for maintainers:

• /sp start - Start an ephemeral machine (takes ~30s)
• /sp stop - Stop a running machine (auto-executed on pr close)

[cursor]

New shared utility duplicates existing local functions

Low Severity

The new baseEventSections in utils.ts duplicates an identical function already defined locally in ~15 existing mapper files (e.g., create_droplet.ts, get_droplet.ts, delete_droplet.ts, assign_reserved_ip.ts, copy_object.ts, etc.). The new GPU mappers import from utils.ts, but all existing mappers still use their own private copies. Introducing a shared version without migrating existing callers means the duplication actually increases — the codebase now has N+1 copies instead of N.

 

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Missing fallback in shared baseEventSections causes empty event sections

Low Severity

The new shared baseEventSections in utils.ts returns an empty array when rootTriggerNode?.componentName is falsy. The established pattern in other mappers (e.g., create_alert_policy.ts) falls back to componentName via rootTriggerNode?.componentName ?? componentName, ensuring event sections are still rendered. This means GPU droplet components will silently show no event sections in edge cases where other components would still display them.