source-salesloft / source-aws-cloudtrail cannot be built: pinned source-declarative-manifest:5.15.0 base image has no `airbyte` user

## What happens

`source-salesloft` and `source-aws-cloudtrail` pin their connector base image to

```
docker.io/airbyte/source-declarative-manifest:5.15.0@sha256:09a84e0622f36393077332faf11cc239e77083fae5fa500592c049dca25888a7
```

That image contains no `airbyte` user, but the generated manifest-only connector Dockerfile ends with `USER airbyte`. Any built image therefore fails to start:

```
docker: Error response from daemon: unable to find user airbyte: no matching entries in passwd file
… returned non-zero exit status 125
```

Verified directly against the base images:

```bash
docker run --rm --entrypoint sh airbyte/source-declarative-manifest:5.15.0 -c 'id airbyte'
# id: 'airbyte': no such user

docker run --rm --entrypoint sh airbyte/source-declarative-manifest:latest -c 'grep airbyte /etc/passwd'
# airbyte:x:1000:1000::/nonexistent:/usr/sbin/nologin
```

## Impact

For both connectors, this blocks anything that builds the image from source:

- the pre-release publish workflow (example run: https://github.com/airbytehq/airbyte/actions/runs/31696602837),
- the connector regression-test harness, which fails at `SPEC` with `Internal failure: true` before `CHECK` / `DISCOVER` / `READ` run,
- the connector's own CI image/spec check.

It is not caused by any particular PR — the pin is the same on master. It surfaced while validating https://github.com/airbytehq/airbyte/pull/84300, where it made the fix impossible to publish or regression-test even though the fix itself is sound.

## Affected connectors

Only two connectors still pin SDM 5.15.0:

- `source-salesloft`
- `source-aws-cloudtrail`

The highest SDM tag pinned anywhere in the monorepo is currently `7.24.0`. Both connectors' last published images predate the tooling change that emits `USER airbyte` (`source-salesloft:1.5.2`, March 2025; `source-aws-cloudtrail:1.1.0`, October 2024), which is why this went unnoticed.

## Suggested fix

Bump the `connectorBuildOptions.baseImage` pin on both connectors to a current `source-declarative-manifest` release (one that defines the `airbyte` user), and publish. Worth also considering a guard in the build tooling so an image whose base lacks the user it is about to switch to fails at build time with a clear message rather than at `docker run`.

---
Found while validating airbytehq/airbyte#84300 on request from the `/ai-prove-fix` workflow run for airbytehq/oncall#13289. Devin session: https://app.devin.ai/sessions/91f66294ee7546e0808dac0f334289b5

---
**Internal Tracking:** https://github.com/airbytehq/oncall/issues/13301