conductoross/conductor-standalone on Docker Hub is 2+ years stale and has more pulls than the current image

## Problem

There are two images in the `conductoross` Docker Hub namespace:

| Image | Latest tag | Last updated | Pulls |
|-------|-----------|--------------|-------|
| `conductoross/conductor` | `3.22.3` | 2026-03-18 | 4,268 |
| `conductoross/conductor-standalone` | `3.15.0` | 2023-12-13 | 4,977 |

`conductor-standalone` is described as *"A standalone container for running Conductor OSS on your local machine"* — exactly what a new user is looking for. It has **more pulls than the current image** but is over 2 years out of date (3.15.0 vs 3.22.3 current).

A new user searching Docker Hub for Conductor, or following an old blog post or Stack Overflow answer, will likely land on `conductor-standalone` and run a badly outdated server without knowing it.

## Options

1. **Deprecate/delete it** — add a deprecation notice pointing to `conductoross/conductor:latest`, then archive or delete the repo
2. **Revive it** — if there's value in a "batteries-included" local-dev image (bundled UI, SQLite, no external deps), start publishing it again on the release cadence

## Affects

- Docker Hub `conductoross/conductor-standalone`
- Any docs, blog posts, or external links referencing the standalone image

Note: There are also confusing images also in orkes-conductor...

These "community" images are also confusing the overall namespace of docker OSS in general.