fix: renumber packagist migration above merged main migrations

V1783382400 predated V1784073600/V1784080000, which landed on main and
merged into this branch after this migration was created. Flyway
requires new versions to be unique and strictly greater than all
existing ones, so applying V1783382400 now would be rejected as
out-of-order. Renumbered to the current epoch.

Signed-off-by: anilb <epipav@gmail.com>

Author: epipav

…ations/V1783382400__packagist_worker.sql …ations/V1784314023__packagist_worker.sqlbackend/src/osspckgs/migrations/V1783382400__packagist_worker.sql renamed to backend/src/osspckgs/migrations/V1784314023__packagist_worker.sql backend/src/osspckgs/migrations/V1783382400__packagist_worker.sql renamed to backend/src/osspckgs/migrations/V1784314023__packagist_worker.sql

@@ -207,5 +207,5 @@ Note: triggering `seed` also chain-starts the full `metadata` drain (set
 `CROWD_PACKAGES_PACKAGIST_STOP_AFTER_FIRST_PAGE=true` locally to bound it).
 Local smoke order: seed → metadata → (rank) → downloads lanes for
 critical-scoped writes. State lives in `packagist_package_state`
-(migration `V1783382400__packagist_worker.sql`); design decisions in
+(migration `V1784314023__packagist_worker.sql`); design decisions in
 `docs/adr/0009-packagist-worker-design-decisions.md`.