feat: 新建 patbond-pet 模块骨架（ADR-009，T2-02 前置）

- 新 Maven 模块挂入父 pom，依赖/插件管理对齐既有 user/auth 模式
  （common 依赖、starter-web/validation/jdbc、exec classifier repackage）
- 骨架内容：PetApplication、/health 探活端点（含 DB 连通检查）、
  GlobalExceptionHandler（同一 {code,message,data} 信封契约）
- 与 user 共库只读写 pet_health schema；不携带 Flyway——单一迁移链
  （V1..V4）仍由 patbond-user 启动时统一执行，flyway_schema_history 不拆
- 配置走 .sample 模式（默认端口 8083，敏感信息经环境变量注入不入库）
- compose 编排纳入 pet 服务（依赖 postgres 健康 + user 先起保证迁移就绪）；
  Dockerfile 与既有服务同模式；Readme 模块清单同步
- 测试：Testcontainers postgres:18 上下文启动冒烟 + /health 探活断言

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

patbond-pet/pom.xml

@@ -0,0 +1,94 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project xmlns="http://maven.apache.org/POM/4.0.0"
+         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
+    <modelVersion>4.0.0</modelVersion>
+
+    <parent>
+        <groupId>com.patbond.patbond</groupId>
+        <artifactId>patbond-api</artifactId>
+        <version>1.0.0-SNAPSHOT</version>
+        <relativePath>../pom.xml</relativePath>
+    </parent>
+
+    <artifactId>patbond-pet</artifactId>
+    <packaging>jar</packaging>
+
+    <name>patbond-pet</name>
+    <description>Pet profile and health record service for Patbond (ADR-009)</description>
+
+    <!-- M2 first-wave skeleton: web + datasource wiring and a liveness endpoint.
+         Flyway is intentionally absent — the single migration chain (V1..V4,
+         including the pet_health schema) is owned and applied by patbond-user,
+         the shared database's startup path. This module only reads/writes the
+         pet_health schema once business endpoints land (M2 second wave). -->
+    <dependencies>
+        <dependency>
+            <groupId>com.patbond.patbond</groupId>
+            <artifactId>patbond-common</artifactId>
+            <version>${project.version}</version>
+        </dependency>
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-web</artifactId>
+        </dependency>
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-validation</artifactId>
+        </dependency>
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-jdbc</artifactId>
+        </dependency>
+        <dependency>
+            <groupId>org.postgresql</groupId>
+            <artifactId>postgresql</artifactId>
+            <scope>runtime</scope>
+        </dependency>
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-test</artifactId>
+            <scope>test</scope>
+        </dependency>
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-testcontainers</artifactId>
+            <scope>test</scope>
+        </dependency>
+        <dependency>
+            <groupId>org.testcontainers</groupId>
+            <artifactId>postgresql</artifactId>
+            <scope>test</scope>
+        </dependency>
+        <dependency>
+            <groupId>org.testcontainers</groupId>
+            <artifactId>junit-jupiter</artifactId>
+            <scope>test</scope>
+        </dependency>
+    </dependencies>
+
+    <build>
+        <plugins>
+            <plugin>
+                <groupId>org.springframework.boot</groupId>
+                <artifactId>spring-boot-maven-plugin</artifactId>
+                <!-- No spring-boot-starter-parent in this build, so the
+                     executable-jar repackaging must be bound explicitly. -->
+                <executions>
+                    <execution>
+                        <goals>
+                            <goal>repackage</goal>
+                        </goals>
+                        <configuration>
+                            <!-- Keep the plain jar as the main artifact so other
+                                 modules can depend on this one; the runnable fat
+                                 jar gets the -exec classifier and is what the
+                                 Dockerfile ships (same pattern as user/auth). -->
+                            <classifier>exec</classifier>
+                        </configuration>
+                    </execution>
+                </executions>
+            </plugin>
+        </plugins>
+    </build>
+</project>