Default vector size is now hardcoded (overrideable via env) in the migration

When migration has already run -> there is no easy way to change the vector size. Current process in volves downgrading the DB via migrationms, setting the `EMBEDDING_DIMENSION` env var and upgarde again.

The default vector size is coded in the migration. A CLI command should be provided to adjust this value and perform a flush.