chore(example): wire stovepipe orchestrator start controller

[mnoah1]

Wires the start controller into the orchestrator sample app.

Why?

Building out overall structure of https://github.com/uber/submitqueue/blob/main/doc/rfc/stovepipe/workflow.md

What?

• Update main.go to include the newly added start controller from branch below this
• This will create a start controller and begin watching for events on the topic. Also adding the validate topic, as start will insert these

Test Plan

• make local-stovepipe-start
• make local-stovepipe-logs
• Insert a sample message:

docker exec -i stovepipe-mysql-queue-1 mysql -uroot -proot submitqueue -e "INSERT INTO queue_messages (topic, partition_key, id, payload, metadata, created_at, published_at, visible_after, failed_at, failure_count, last_error, original_topic) VALUES ('start', 'github.com/uber/cadence', CONCAT('manual-', CAST(UNIX_TIMESTAMP(NOW(3)) * 1000 AS UNSIGNED)), '{\"uri\":\"git://github.com/uber/cadence/refs/heads/main/abc123def456\",\"partition_key\":\"github.com/uber/cadence\"}', NULL, CAST(UNIX_TIMESTAMP(NOW(3)) * 1000 AS UNSIGNED), CAST(UNIX_TIMESTAMP(NOW(3)) * 1000 AS UNSIGNED), 0, 0, 0, '', '');"
mysql: [Warning] Using a password on the command line interface can be insecure.

• Confirm via logs that the message is receives and enqueues the validate message:

orchestrator-service-1  | 2026-06-18T13:21:59.727Z	DEBUG	queue_mysql.message_store	mysql/message_store.go:217	fetched messages	{"topic": "start", "partition_key": "stovepipe-monorepo", "count": 1}
orchestrator-service-1  | 2026-06-18T13:21:59.732Z	DEBUG	consumer/consumer.go:351	processing delivery	{"controller": "start", "topic_key": "start", "message_id": "stovepipe-monorepo/1", "partition_key": "stovepipe-monorepo", "attempt": 1}
orchestrator-service-1  | 2026-06-18T13:21:59.732Z	INFO	start_controller	start/start.go:97	received ingest request	{"spid": "stovepipe-monorepo/1", "queue": "stovepipe-monorepo", "change_uris": ["git://git.example.com/uber/monorepo/refs%2Fheads%2Fmain/abcdef0123456789abcdef0123456789abcdef01"], "change_count": 1, "attempt": 1, "partition_key": "stovepipe-monorepo"}
orchestrator-service-1  | 2026-06-18T13:21:59.732Z	DEBUG	queue_mysql.message_store	mysql/message_store.go:72	inserting messages	{"topic": "validate", "count": 1, "visible_after": 0}
orchestrator-service-1  | 2026-06-18T13:21:59.740Z	DEBUG	queue_mysql.message_store	mysql/message_store.go:125	inserted messages	{"topic": "validate", "count": 1}
orchestrator-service-1  | 2026-06-18T13:21:59.740Z	DEBUG	queue_mysql.publisher	mysql/publisher.go:65	published message	{"topic": "validate", "message_id": "stovepipe-monorepo/1"}
orchestrator-service-1  | 2026-06-18T13:21:59.740Z	INFO	start_controller	start/start.go:115	published ingest request to validate	{"spid": "stovepipe-monorepo/1", "topic_key": "validate"}

• main.go doesn't have tests of its own but we can get some e2e tests in place for stovepipe separately