fix: renumber migrations to resolve duplicate version 003

Author: Anubhav Singh

…grations/003_slippage_tolerance.down.sql …grations/004_slippage_tolerance.down.sqlbackend/src/db/migrations/003_slippage_tolerance.down.sql renamed to backend/src/db/migrations/004_slippage_tolerance.down.sql backend/src/db/migrations/003_slippage_tolerance.down.sql renamed to backend/src/db/migrations/004_slippage_tolerance.down.sql

@@ -1,2 +1,2 @@
--- Migration: 003_slippage_tolerance (down)
+-- Migration: 004_slippage_tolerance (down)
 ALTER TABLE portfolios DROP COLUMN IF EXISTS slippage_tolerance;

…migrations/003_slippage_tolerance.up.sql …migrations/004_slippage_tolerance.up.sqlbackend/src/db/migrations/003_slippage_tolerance.up.sql renamed to backend/src/db/migrations/004_slippage_tolerance.up.sql backend/src/db/migrations/003_slippage_tolerance.up.sql renamed to backend/src/db/migrations/004_slippage_tolerance.up.sql

@@ -1,4 +1,4 @@
--- Migration: 003_slippage_tolerance (up)
+-- Migration: 004_slippage_tolerance (up)
 -- Add slippage_tolerance to portfolios (0.5 - 5 percent, default 1).
 
 ALTER TABLE portfolios