feat: Support ECS Managed Daemons

[guikcd]

Add ECS Managed Daemons support

Summary

Adds full support for ECS Managed Daemons (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/managed-daemons.html), a new AWS feature that deploys cross-cutting software agents independently across ECS infrastructure using dedicated daemon task definitions.

SDK upgrade

• aws-sdk-go-v2/service/ecs v1.74.0 → v1.83.0 (first version with daemon APIs)

New views

• Daemon list view (accessible from cluster via Shift+M)
• Daemon task definition view (accessible from daemon via Enter/t, or from a daemon task in cluster tasks via t)

New API layer (internal/api/daemon.go)

• ListDaemons — list daemons in a cluster
• DescribeDaemon — get daemon detail
• ListDaemonTaskDefinitions — list revisions for a daemon task definition family
• DescribeDaemonTaskDefinition — describe a specific revision
• DescribeDaemonRevisions — resolve daemon → task definition family

Cluster view

• Added "Daemons" column showing the count of managed daemons per cluster

Navigation

• Shift+M from cluster view → daemon list
• Enter or t from daemon list → daemon task definitions
• t from a daemon task (in cluster tasks view) → daemon task definition (instead of regular task definition)
• d to describe daemons and daemon task definitions as JSON
• Standard back navigation (Esc/h)

GitHub Actions

• Bump checkout & setup-go Actions to update to node 24:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Code assisted with Kiro-cli