403/fix deployment failure due to migration desynchronization

[YuraPetrovskyi]

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review on my code
• New and previously existing unit tests pass locally with my changes

Description

Relates #403

This PR resolves the deployment failure caused by migration desynchronization after merging all migrations into a single file.

Solution:

• Removed outdated migration files.
• Reverted outdated migrations using supabase migration repair --status reverted <migration_ids>
• Pulled the current schema using supabase db pull
• Fixed supabase_admin ownership issue by removing unnecessary statements in migration files:
  ALTER PUBLICATION "supabase_realtime_messages_publication" OWNER TO "supabase_admin";
• Created a new migration file to set avatar column as NOT NULL with a default value.

Files changed

Removed:

• supabase/migrations/20241128133000_schema_v2_start.sql
• supabase/migrations/20250124193148_non-nullable-profile-avatar.sql

Added:

• supabase/migrations/20250207173330_remote_schema.sql
• supabase/migrations/20250208135136_add-non-nullable-avatar.sql

UI changes

• No UI changes were made in this PR.

Changes to Documentation

• No documentation changes were required.

Tests

• All existing and new tests passed successfully.
• Manually verified that migration history is now synchronized with the remote database.

[netlify]

👷 Deploy request for cool-creponne-3e1272 pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	1dcc37b

[OlenaReukova]

All core functions work correctly
Migrations execute without errors
Database schema is synchronised
Previous deployment issues are resolved.

@YuraPetrovskyi, it looks good.