Add property closeConnOnFatalError to match HikariCP's behavior

[linghengqian]

• Add property closeConnOnFatalError to match HikariCP's behavior.
• Fixes connection disabled when use com.alibaba.druid.pool.DruidDataSource apache/shardingsphere#32765 .
• Also fixes [BUG] connection disabled #6050 . Also fixes 最新版1.2.23版本出现connection closed错误 #5963 . Also fixes 有解决方案吗？ #4188 . Also fixes keepalive还是有断开 #4013 . Also fixes The connection pool shouldn't close a connection after an exception #3626 . Also fixes 连接无法获取 #2404 .
• By setting closeConnOnFatalError to false, Druid's behavior will align with HikariCP, that is, the connection will no longer be closed when a fatal error defined by Druid occurs. This solves a series of controversies surrounding Spring Boot, Hibernate, Flyway, and ShardingSphere. This is a huge regret introduced from 882470b 7 years ago.

dataSources:
  db:
    dataSourceClassName: com.alibaba.druid.pool.DruidDataSource
    driverClassName: com.mysql.cj.jdbc.Driver
    url: jdbc:mysql://127.0.0.1:3306/demo_ds?serverTimezone=UTC
    username: root
    password: 
    closeConnOnFatalError: false

• Also see com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException flyway/flyway#2240 (comment) .

The connection pool shouldn't close a connection after an exception. Please file an issue with them.