fix(clickhouse): renumber the external deployment id migration to 041

040 was already claimed by 040_create_task_events_search_v2.sql (#4615) by the
time #4661 landed, so `goose up` panics with "duplicate version 40 detected"
while collecting the migration directory and applies nothing.

Renumber this one rather than the other: goose keys on the version number and
not the filename, so version 40 is already recorded wherever 040 has been
applied, and renaming that file would re-run an applied migration. This one has
never been applied anywhere, because collection aborts before any SQL runs.

Author: 0ski