ZMySQLDA: reconnect on mariadb's Connection was killed

After server restarts, mariadb uses an error 1927 which is mariadb
specific, with no corresponding constant in CR module when server
restart. This is the case at least with mariadb 10.3.38.

This fix the following problem:
 - start zope and use mariadb connection
 - restart mariadb
 - use mariadb connection again, see an error:
    Error Type: OperationalError
    Error Value: (1927, 'Connection was killed')

This change to treat 1927 as an error for which we can reconnect and
retry the query. Some other connectors do it, for example sqlalchemy in
https://github.com/sqlalchemy/sqlalchemy/issues/5493
Status Job ID Name Coverage
  External
passed ERP5.CodingStyleTest-Master

03:09:33

passed ERP5.PerformanceTest-Master

00:40:05

failed ERP5.UnitTest-Master

04:02:28

failed ERP5.UnitTest-Zope2

05:21:59

passed SlapOS.Eggs.UnitTest-Master.Python2

00:28:13

passed SlapOS.Eggs.UnitTest-Master.Python3

00:18:23

passed Wendelin.UnitTest-Master

01:12:59

passed ERP5.PerformanceTest-Master

01:08:25

passed SlapOS.Eggs.UnitTest-Master.Python2

00:41:10

passed SlapOS.Eggs.UnitTest-Master.Python3

00:19:17

passed SlapOS.Eggs.UnitTest-Master.Python3

00:22:05

passed Wendelin.UnitTest-Master

02:43:02