fix(platform): update bridge task url after github org rename

[jgrant-sms]

Overview

The GitHub org was renamed from sst to anomalyco, making the bridge-task container image inaccessible at its hardcoded URL. This breaks Task dev mode (sst dev with sst.aws.Task) because ECS cannot pull the image.

Production deployments are unaffected since they use the user's own Docker image.

Changes

• Update bridge-task image URL from ghcr.io/sst/sst/ to ghcr.io/anomalyco/sst/ in platform/src/components/aws/task.ts
• Update build script to push to the new registry location in platform/scripts/build

Fixes #6307

Steps to reproduce

1. Run sst dev with a Task component (e.g., examples/aws-task)
2. Trigger the task via the linked Lambda function
3. The ECS task fails with:
   CannotPullContainerError: failed to resolve ref ghcr.io/sst/sst/bridge-task:20241224005724:
   failed to authorize: 403 Forbidden

Steps to validate the fix

# Build and link the SDK
cd sdk/js
bun install
bun run build
bun link

# Set up the example
cd ../examples/aws-task
bun link sst

# Run dev mode
go run ../../cmd/sst dev

# Trigger the task via the Lambda URL shown in output
curl <lambda-url>

The task should execute successfully without the CannotPullContainerError.

[mikechabot]

While this PR is pending, I was able to workaround this without rebuilding the underlying sst dependency.

Navigate to .sst/platform/src/components/aws/task.ts, and update the containers argument passed to createTaskDefinition:

return [
  {
    ...v[0],
    image: output(
      "ghcr.io/anomalyco/sst/bridge-task:20241224005724", // Updated image URL
    ),
    environment: {
      ...v[0].environment,
      SST_TASK_ID: name,
      SST_REGION: process.env.SST_AWS_REGION!,
      SST_APPSYNC_HTTP: appsync.http,
      SST_APPSYNC_REALTIME: appsync.realtime,
      SST_APP: $app.name,
      SST_STAGE: $app.stage,
    },
  },
];