refactor: 빌드 최적화 및 ci 수정

src/adapter/outbound/persistence-jpa/build.gradle

@@ -1,9 +1,11 @@
+plugins {
+    id 'ca.spring-library'
+    id 'ca.spring-config'
+    id 'java-test-fixtures'
+    id 'ca.jpa-evidence'
+}
+
 // Shared test code as a Gradle test-fixtures variant — ADR-BUILD-001.
-apply plugin: 'ca.spring-library'
-apply plugin: 'ca.spring-config'
-
-apply plugin: 'java-test-fixtures'
-
 // JPA persistence adapter — merged RDBMS base + PostgreSQL vendor module.
 // Owns JPA entities, Spring Data repositories, mappers, transaction/audit/lock/outbox port
 // implementations, and the vendor-neutral SPI interfaces (OutboxClaimRepository /
@@ -29,8 +31,6 @@ strictTestLanes {
     sourceSet('jpaPlatformPerformanceTest') { compilesAgainst 'main', 'testFixtures' }
 }
 
-ext.jpaPostgreSqlEvidenceImage = 'postgres:16-alpine'
-
 dependencies {
     implementation project(':application-core')
     implementation project(':shared-contract')
@@ -108,6 +108,8 @@ dependencies {
 // through `requires(...)` turns on `failOnNoMatchingTests` AND the post-run check that the named
 // selector actually executed, so a renamed readiness class fails its lane instead of leaving it
 // with nothing to run.
+String jpaPostgreSqlEvidenceImage = providers.gradleProperty('jpaPostgreSqlEvidenceImage')
+        .getOrElse('postgres:16-alpine')
 String readinessPackage = 'dev.caskeleton.adapter.outbound.persistence.readiness'
 Map<String, String> postgresqlReadinessLanes = [
         postgresqlLifecycleIntegrationTest             : 'PostgreSqlLifecycleIntegrationTest',
@@ -155,7 +157,7 @@ strictTestLanes.lanes.named('postgresqlSecurityBaselineIntegrationTest').configu
 }
 
 // The task itself stays, and its name is not negotiable: config/jpa/readiness-cards.yaml lists it as
-// a support task of the `jpa-security-baseline` card, and gradle/jpa-evidence.gradle resolves every
+// a support task of the `jpa-security-baseline` card, and the ca.jpa-evidence qualification plugin resolves every
 // listed path through `tasks.findByName` and fails the build when one is missing. What changed is
 // what it checks. Grepping the fixture's source text for 'runtimeRoleCannotCreateInApplicationSchema',
 // 'assertDockerAvailable' and '42501' passed on three strings in a comment and proved nothing about
@@ -355,11 +357,11 @@ apiSurface {
     ]
 }
 
-apply from: rootProject.file('gradle/jpa-evidence.gradle')
+
 
 // The JPA readiness registry describes this platform's lanes and resolves their task paths, so it
 // runs with this leaf's `check` rather than with all 62. The task itself is registered by
-// gradle/qualification/jpa-qualification.gradle, which the root applies.
+// the ca.jpa-qualification plugin from build-qualification, which the root applies.
 tasks.named('check') {
     dependsOn rootProject.tasks.named('verifyJpaReadinessRegistry')
 }