Add deep analysis doc for client-side session reuse and index it under analysis

[Copilot]

This PR documents what is required to support client-side persistent JDBC session reuse in OJP (avoiding connect/terminateSession per-request overhead), including constraints around bounded retention and queued/in-flight work awareness.
It captures architectural impact, rollout guidance, and risk boundaries so implementation can proceed from a clear decision baseline.

• New analysis document

  • Added documents/analysis/CLIENT_SIDE_SESSION_REUSE_ANALYSIS.md.
  • Covers:
    • current verified lifecycle behavior (connect fast path vs close -> terminateSession)
    • required driver/server changes (lease manager, close semantics split, sanitization, limits, observability)
    • multinode/XA scope boundaries
    • risks, phased rollout, and explicit opinions/suggestions/questions/concerns.

• Analysis index update

  • Updated documents/analysis/README.md to include the new document under a dedicated Session Lifecycle & Reuse section.
  • Updated the index “Last Updated” date.

Example index entry added:

### Session Lifecycle & Reuse

- [CLIENT_SIDE_SESSION_REUSE_ANALYSIS.md](./CLIENT_SIDE_SESSION_REUSE_ANALYSIS.md) - Analysis of client-side persistent session reuse, required architecture changes, limits, risks, and rollout approach

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud