Use `DataIntegrityViolationException` instead of `DuplicateKeyException` as it is recommended by its Javadocs

[artembilan]

Apparently some databases don't throw a proper code to identify a DuplicateKeyException, so better to catch DataIntegrityViolationException with the same meaning.

See more info in: https://stackoverflow.com/questions/78142353/spring-integration-and-spring-batch-transaction-manager-collision