test(sp32): bump migration version assertions to 19

backend/tests/test_db_migrate.py

@@ -124,14 +124,16 @@ def test_migration_latest_idempotent_on_fresh_db(tmp_path: Path) -> None:
     SP27 Task 17 bumped it to 17 with the patient_control_number
     backfill UPDATE (the migration runner now applies DML too).
     SP28 bumped it to 18 with the claim_acks join table.
+    SP32 bumped it to 19 with rendering_provider_npi +
+    service_provider_npi on claims and remittances.
     """
     engine = _fresh_engine(tmp_path)
     db_migrate.run(engine)
     v_after_first = _user_version(engine)
-    assert v_after_first == 18, f"expected head=18, got {v_after_first}"
+    assert v_after_first == 19, f"expected head=19, got {v_after_first}"
 
     db_migrate.run(engine)
-    assert _user_version(engine) == 18, "second run should not bump version"
+    assert _user_version(engine) == 19, "second run should not bump version"
 
 
 def test_drop_claims_unique_constraint_migration(tmp_path: Path, monkeypatch: pytest.MonkeyPatch) -> None:
@@ -157,7 +159,7 @@ def test_drop_claims_unique_constraint_migration(tmp_path: Path, monkeypatch: py
     engine = _fresh_engine(tmp_path)
 
     db_migrate.run(engine)
-    assert _user_version(engine) == 18, f"expected head=18, got {_user_version(engine)}"
+    assert _user_version(engine) == 19, f"expected head=19, got {_user_version(engine)}"
 
     # Two claims in one batch with the same patient_control_number
     # must be insertable. If 0015's table recreation re-introduced a