fix(flyway): add explicit personne schema prefix to migration

Flyway's defaultSchema only controls where flyway_schema_history is created,
not the search_path for migration scripts. Without explicit schema prefixes,
tables were created in public schema while the application queries personne.

This fix ensures all future deployments create tables in the correct schema.

Author: npasquin

assembly/src/main/resources/db/migration/V1__connaissance_client.sql

@@ -1,5 +1,7 @@
--- Create connaissance_client table
-CREATE TABLE IF NOT EXISTS connaissance_client
+-- Create connaissance_client table in personne schema
+-- Note: Flyway defaultSchema=personne only affects flyway_schema_history location,
+-- not the search_path for migration scripts. We must explicitly specify schema.
+CREATE TABLE IF NOT EXISTS personne.connaissance_client
 (
     id_personne              BIGINT       NOT NULL,
     tenant_id                VARCHAR(50)  NOT NULL,
@@ -10,8 +12,8 @@ CREATE TABLE IF NOT EXISTS connaissance_client
     CONSTRAINT connaissance_client_unique_person_tenant UNIQUE (id_personne, tenant_id)
 );
 
--- Create historique table
-CREATE TABLE IF NOT EXISTS connaissance_client_historique
+-- Create historique table in personne schema
+CREATE TABLE IF NOT EXISTS personne.connaissance_client_historique
 (
     id            uuid         NOT NULL,
     id_personne   BIGINT       NOT NULL,
@@ -23,12 +25,12 @@ CREATE TABLE IF NOT EXISTS connaissance_client_historique
 );
 
 -- Ensure uniqueness on historique id
-ALTER TABLE connaissance_client_historique
+ALTER TABLE personne.connaissance_client_historique
     ADD CONSTRAINT connaissance_client_historique_id_unique UNIQUE (id);
 
 -- Add composite foreign key from historique to connaissance_client (id_personne, tenant_id)
-ALTER TABLE connaissance_client_historique
+ALTER TABLE personne.connaissance_client_historique
     ADD CONSTRAINT fk_historique_connaissance_client
         FOREIGN KEY (id_personne, tenant_id)
-            REFERENCES connaissance_client (id_personne, tenant_id)
+            REFERENCES personne.connaissance_client (id_personne, tenant_id)
             ON DELETE RESTRICT ON UPDATE RESTRICT;