Fix: API DELETE container skips Proxmox deletion

[Copilot]

When deleting a container via the JSON API, only the database record was removed — the Proxmox LXC container was left alive. The isApiRequest branch bypassed all Proxmox cleanup logic that existed in the browser form path.

Changes

• Include Node association in the API path's container query so the Proxmox API client can be constructed
• Add Proxmox deletion via api.deleteContainer() with force=true, purge=true before DB destroy
• Add hostname safety check via api.lxcConfig() — returns 409 JSON on mismatch instead of silently skipping or redirecting

// Before
if (isApiRequest(req)) {
  const container = await Container.findByPk(containerId);
  await container.destroy(); // only DB — Proxmox container left running
  return res.status(204).send();
}

// After
if (isApiRequest(req)) {
  const container = await Container.findOne({
    where: { id: containerId },
    include: [{ model: Node, as: 'node' }]
  });
  // hostname mismatch → 409
  await api.deleteContainer(node.name, container.containerId, true, true);
  await container.destroy();
  return res.status(204).send();
}

[runleveldev]

@copilot this is repetitive with code elsewhere in the router. Minimize repetition rather than minimizing changes.

[Copilot]

@copilot this is repetitive with code elsewhere in the router. Minimize repetition rather than minimizing changes.

Refactored in d080fc0. Extracted a deleteContainerFromProxmox(container) helper that owns the Proxmox lxcConfig check + deleteContainer call, then unified the two separate API/non-API branches into a single handler. The branches now only diverge where the response format actually differs (JSON vs redirect).

[runleveldev]

Implemented in #269