fix: force-pull images on install and fix provisioning test assertions

Installers now use `--pull always --force-recreate` on `docker compose up`
to ensure fresh images are used on every install/reinstall, preventing
stale containers from missing schema changes like db_password.

Fix VendorTenantServiceTest to expect two repository saves in provisioning
tests (one for dbPassword, one for final status).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

src/test/java/net/siegeln/cameleer/saas/vendor/VendorTenantServiceTest.java

@@ -33,6 +33,7 @@ import static org.assertj.core.api.Assertions.assertThatThrownBy;
 import static org.mockito.ArgumentMatchers.any;
 import static org.mockito.ArgumentMatchers.eq;
 import static org.mockito.Mockito.never;
+import static org.mockito.Mockito.times;
 import static org.mockito.Mockito.verify;
 import static org.mockito.Mockito.when;
 
@@ -153,7 +154,7 @@ class VendorTenantServiceTest {
         assertThat(tenant.getStatus()).isEqualTo(TenantStatus.ACTIVE);
         assertThat(tenant.getServerEndpoint()).isEqualTo("http://server:8080");
         assertThat(tenant.getProvisionError()).isNull();
-        verify(tenantRepository).save(tenant);
+        verify(tenantRepository, times(2)).save(tenant);
     }
 
     @Test
@@ -175,7 +176,7 @@ class VendorTenantServiceTest {
         // provisionAsync modifies the tenant entity in-place (runs synchronously in unit tests)
         assertThat(tenant.getProvisionError()).isEqualTo("Docker failure");
         assertThat(tenant.getStatus()).isEqualTo(TenantStatus.PROVISIONING);
-        verify(tenantRepository).save(tenant);
+        verify(tenantRepository, times(2)).save(tenant);
     }
 
     @Test