Create rules for JDBC exception translator

According to the [migration guide](https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-6.x#data-access-and-transactions-1):

> Spring's default JDBC exception translator is the JDBC 4 based SQLExceptionSubclassTranslator now, detecting JDBC driver subclasses as well as common SQL state indications (without database product name resolution at runtime). As of 6.0.3, this includes a common SQL state check for DuplicateKeyException, addressing a long-standing difference between SQL state mappings and legacy default error code mappings.

Investigate and create rules if necessary.

In the rule description and message, try to be as verbose and clear as possible. Code examples are always welcome and useful. Feel free to use markdown syntax for these.

Start with the linked Spring Framework 6 migration-guide section, then inspect existing Spring and JDBC rule definitions in this repository for their structure and tests. Determine whether rules are needed for the JDBC exception translator changes; done means any necessary rules have clear, verbose descriptions and messages, with useful Markdown examples.

Written by the indexing model from the issue text.