Extends the existing TiDB orphan-COM_STMT_EXECUTE sample with an
HTTP endpoint that exercises Apache Pulsar's RoundRobinPartition
routing — the producer-side behaviour that triggers keploy's
partition-suffix replay mismatch (keploy/enterprise#2064).

The bean shape, JDBC parameters and JPA settings replicate the
Flipkart Global-Shipment-Master service's production config so a
recording captured against this sample produces mocks structurally
identical to the customer's:

  * HikariCP autoCommit=false paired with
    spring.jpa.properties.hibernate.connection.provider_disables_autocommit=true
  * JDBC URL: useServerPrepStmts=true&cachePrepStmts=true
              &prepStmtCacheSize=500&prepStmtCacheSqlLimit=2048
  * Hibernate MySQLDialect (TiDB is wire-compatible on :4000),
    open-in-view=false
  * Pulsar producer with MessageRoutingMode.RoundRobinPartition
    against an 8-partition topic pre-created by the
    docker-compose pulsar-init container

New endpoint: POST /events/patch — JPA-saves an Event row through
TiDB then synchronously publishes the payload to the partitioned
topic; mirrors the Flipkart endpoint shape exactly so the customer's
mocks.yaml can be replayed against this sample.

Existing /api/kv/* endpoints (orphan-EXECUTE scenario) are unchanged.

Additions:
  * EventEntity / EventRepository: JPA persistence, Hibernate
    auto-DDL creates the `events` table.
  * PulsarConfig: PulsarClient + Producer<byte[]> beans.
  * EventsController: @transactional POST /events/patch.
  * docker-compose: Apache Pulsar 4.0.3 standalone + one-shot
    pulsar-init that creates the partitioned topic.
  * Dockerfile: two-stage Maven -> JRE 17 build.
  * k8s/ manifests: namespace, TiDB Deployment+Service, Pulsar
    Deployment+Service+Job, app Deployment+Service with
    keploy.io/record-session=true for the static webhook.
  * README: walkthroughs for the local docker-compose smoke path
    and the in-cluster k8s-proxy auto-replay path.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>