SRE-627: match hibernate exception handling in jooq

[vitaly-block]

Hoist hibernate-like exception handling to misk-jdbc to cover other providers with the same logic

Description

Refactored the TransactionRetryHandler to make database exception retry logic specific to the database type being used.
Database-Specific Retry Logic: Retryable exceptions are now only checked for the configured database type:

• Connection closed exceptions remain retryable for all databases
• Vitess-specific exceptions only retry when DataSourceType.VITESS_MYSQL is configured
• CockroachDB-specific exceptions only retry when DataSourceType.COCKROACHDB is configured
• TiDB-specific exceptions only retry when DataSourceType.TIDB is configured

API Changes

New Constructor: Added convenient TransactionRetryHandler(qualifierName, databaseType) constructor for easy database type-specific configuration
Backward Compatibility: Existing constructors and APIs remain unchanged

// Before: All database exceptions checked regardless of database type
isMessageRetryable(th)

// After: Database type-specific checking
isConnectionClosed(th) ||
  (databaseType == DataSourceType.VITESS_MYSQL && isRecoverableVitessException(th)) ||
  (databaseType == DataSourceType.COCKROACHDB && isRecoverableCockroachException(th)) ||
  (databaseType == DataSourceType.TIDB && isRecoverableTidbException(th))

There should be no breaking changes, existing code should work:

// Old (still works)
TransactionRetryHandler("mydb")

// New (recommended)
TransactionRetryHandler("mydb", DataSourceType.VITESS_MYSQL)

Testing Strategy

New test cases included, https://gradle.com/s/7wbp6xzb5nt4q

Checklist

• I have reviewed this PR with relevant experts and/or impacted teams.
• I have added tests to have confidence my changes work as expected.
• I have a rollout plan that minimizes risks and includes monitoring for potential issues.

[aparajon]

There are quite a bit of other retryable message strings that we may want to include here that are in our JSC component. Perhaps worth a follow-up PR if we want to keep this PR simpler