LP:761603 - Innodb and other errors must cause assertions in debug mode

Certain errors, in InnoDB and out of it are simply printed to STDOUT. Instead, in a debug build, an assertion should be raised. This will allow such errors to be detected more easily in automated testing, especially since their format is not unified and therefore it is difficult to simply watch the log file during the test. An assertion is much more easier to test, simplfy and debug.

In particular, the following errors have been observed:

InnoDB: Error: row_search_for_mysql() is called without ha_innobase::external_lock()
110415 13:32:28 [ERROR] trx->active_flag & TRX_ACTIVE_IN_MYSQL== 0, but trx->conc_state != TRX_NOT_STARTED

so please convert:

• All errors that look like those two (that is, transaction and handler related) and
• All errors printed inside innodb regardless of the actual text