#13924: in Iceberg catalog, JdbcTableOperations should catch and handle PostgresSQL's exception for duplicated keys

[sqd]

Fixes #13924

Previously reviewed at #13925 (fixed all the suggestions in there)

[RussellSpitzer]

Don't we need a similar fix in ViewOperations?
JDBCCatalog has a similar check in renameTable and renameView

It may be best to pull this bit of logic out into a utility method and ditch the magic string.

  static boolean isConstraintViolation(SQLException e) {
    return e instanceof SQLIntegrityConstraintViolationException
        || POSTGRES_UNIQUE_VIOLATION_SQLSTATE.equals(e.getSQLState())
        || (e.getMessage() != null && e.getMessage().contains("constraint failed"));
  }

  static void handleCommitSqlException(
      SQLException e, String currentMetadataLocation, String entityType, Object identifier) {
    if (isConstraintViolation(e)) {
      if (currentMetadataLocation == null) {
        throw new AlreadyExistsException(e, "%s already exists: %s", entityType, identifier);
      } else {
        throw new UncheckedSQLException(e, "%s already exists: %s", entityType, identifier);
      }
    }

    throw new UncheckedSQLException(e, "Unknown failure");
  }

We also need a test of the new pathway, should be a pretty simple mock I think?

[sqd]

Good point. I extrapolated that out and added a few tests.