mysqldump not always handling SHOW CREATE TRIGGER failures correctly

When a "SHOW CREATE TRIGGER" stamement issued by mysqldump fails, mysqldump automatically assumes that this can only happen due to the server version being too old, and so the SHOW CREATE TRIGGER syntax not being available yet, as it was the case for pre-5.5 MySQL.

I'm handling a case right now where the server clearly supports the syntax, so that SHOW CREATE TRIGGER must have failed for some other reason (which is not known yet).

mysqldump simply applies a catch-all method to all query failures here, falling back to trying to extract trigger information from SHOW CREATE TRIGGERS (note the plural form), and in my case crashes at this attempt.

mysqldump should be more clever here, and only fall back to the backward compatibility mode on actual query syntax errors, but should show the actual server error message and terminate on any other error codes.