fix(db): re-version the eba autovacuum migration past its later-merged siblings (#3387)

The three same-morning autovacuum migrations merged in reverse timestamp
order — envs (…051152) and snapshots (…051151) landed ~4h before
env_build_assignments (…051130). Any database that migrated in that
window is at …051152 and goose (no -allow-missing) now refuses with
'found 1 missing migrations before current version'. Renaming the eba
migration to a fresh timestamp converges every state: databases past
…051152 apply it next; databases that already applied …051130 (fresh CI
DBs) re-apply it, which is safe — ALTER TABLE SET storage parameters is
idempotent; databases before all three (production) apply everything in
clean order and never see the gap. Same remedy class as the #3369
collision. File content unchanged.

Author: ValentaTomas